A message, reminder or sticker did not arrive

Troubleshooting

A message, reminder or sticker did not arrive

Distinguish audience, queue state, Telegram confirmation and schedule eligibility.

Who can use it: Communications and Sticker Drops operators
Where to find it: The relevant Broadcasts, Inbox, Launch Watch or Sticker Drops history
Before you start: Access to the affected project

On this page

Check in this order

Identify the channel: group broadcast, watcher DM, one Inbox reply, pack publication or recurring drop.
Confirm the selected project and exact target group, launch or conversation.
Read the operation’s returned status and history. Queued or processing is not confirmed delivery.
For group sends, Re-check status and permissions. For watcher sends, inspect active opt-ins and relevant member eligibility/preferences.
For countdowns, inspect the saved schedule, device timezone, Launch approaching state and due time.
For Sticker Drops, inspect Enabled/Paused, project emergency pause, time window, cap, published pack and Delivery history. Allow for the five-minute scheduler check.
If the outcome is unconfirmed, check the actual Telegram destination where you can before retrying. Use a provided safe retry instead of creating duplicate sends.

Common causes

Item	Details
Broadcast rejected	Text/caption length or saved logo requirements; branded total is 1,024 characters.
Watcher audience smaller than group	Only explicit eligible watch opt-ins are included.
Countdown missed	The launch was not armed before the due time or the member disabled countdowns.
Sticker Drops late	Scheduler cadence, cap, active window, pause or bot error.
Inbox thread absent	Capture off, command/group message, or ambiguous relationship across projects.

Do not assume

A saved schedule is not a watcher announcement. Published pack is not a recurring drop. Motion Live is not a community message. A successful contract registration is not a watcher notification.