Skip to content
SHOPIFY PRODUCTS. DISCORD COMMUNITIES.EARLY ACCESS IS OPEN ↗
memberport
← The journal

Troubleshooting / PRACTICAL LAUNCH NOTES

Your Shopify drop did not appear in Discord. Check these five things.

Find where a product announcement stopped: the saved drop, scheduled time, selected channel, bot permissions, or product readiness.

A saved drop and a delivered message are different states. If your Shopify announcement has not appeared in Discord, start with one drop and find the last step that completed. Changing several settings at once makes the actual cause harder to identify.

1. Confirm that the drop was supposed to send.

Check whether the drop is manual, scheduled, or paused. Saving a manual drop prepares it; it is not the same action as announcing it. For a schedule, compare the saved date, time, and displayed time zone with the moment you expected.

Keep the current status and any error visible while you investigate. Record the actual wording. “Discord is broken” is not enough information to distinguish a paused launch from a permission failure.

What you observeCheck firstUseful next step
Saved but no messageManual versus scheduled modeConfirm whether an announcement was requested
Scheduled for laterDate, time, and time zoneWait for the intended launch or correct the schedule
PausedThe drop’s enabled stateDecide whether to resume it
An error is shownThe exact error textResolve that condition before retrying
Message in another channelSaved destinationConfirm the channel before another send

2. Check the selected channel.

MemberPort sends to the announcement channel selected in Setup. Confirm both the server and the channel. Similar channel names in different servers can make a successful announcement appear to be missing.

The current app accepts a text or announcement channel in the connected server. If someone deleted and recreated a channel with the same name, revisit Setup. A familiar label does not prove the saved destination is still the same channel.

Also consider the audience. A message posted in a private staff channel will be invisible to ordinary customers even when the bot delivered it correctly. Inspect the destination before changing the product list.

3. Inspect the bot’s effective permissions.

For MemberPort’s current product cards, the bot needs View Channels, Send Messages, and Embed Links in the selected channel. Its message-creation operation requires permission to send; denying visibility also prevents normal channel actions. Check that exact destination rather than another channel where the bot works.

A channel can have permissions that differ from the server role or its category. Discord’s documentation explains that a channel which is not synced with its category will not automatically follow later category changes. If the server was reorganised recently, inspect the current settings directly.

Do not add Administrator or reorganise customer access roles as a first response. MemberPort’s current announcements do not require a membership-role system. Apply the permissions needed for channel messages, then check the original failure again.

4. Review the selected products.

Use the app’s preview to check the intended product names and direct links without sending a message. If no products are eligible to announce, review the selection and Shopify status. Use the activation option only if you intend those selected products to become Active before the announcement.

If a message appears but its product link fails for shoppers, the next task is storefront readiness. Product activation and sales-channel publication are separate. Check the customer-facing destination instead of sending another copy of the message.

5. Make a deliberate retry.

After fixing the problem, inspect the destination before retrying. A delayed screen response does not prove that no message arrived. Keep one person responsible for the retry and avoid creating another drop for the same release while the first is being investigated.

Follow any instruction about a delivery that has already started in a particular channel. Moving the destination is not a general repair for an incomplete send. Record what changed so a later support review can distinguish the original attempt from the retry.

If you need help, share the drop name, intended time and zone, selected server and channel, current status, exact error, and whether any message appeared. Include the settings you already changed. Do not send Shopify access tokens, Discord bot tokens, passwords, or customer data.

Sources & further reading

MAKE YOUR NEXT DROP A MOMENT

A product launch
your community can find.

Plan selected Shopify products, the Discord channel, and the announcement time with MemberPort.

Request early access