Skip to content

Sending queue

The sending queue is one list of the messages your workspace has queued or already tried to send: Telegram messages from chats, campaigns, AI agents, bots, surveys and the API, plus every campaign step on email, X and social. Open it when you want to know what goes out next, or why something did not.

Plan
All plans

Nothing is sent directly from the screen where you write it. A Telegram message becomes a queued job with a send time, and a background worker delivers due jobs one after another, in order of their send time. Campaign steps on email, X and social wait in their campaign until they are due, and are sent by the campaign engine.

The page has four views:

ViewWhat it shows
QueuedEverything still waiting, grouped into Due now, Today, Tomorrow and Later, with the time each one goes out
SentWhat went out, with how many were sent in the last 24 hours
FailedWhat could not be sent, each with the reason
All historySent, failed and skipped messages together

Each row shows the recipient, the channel, the first words of the message, what queued it and the account it goes out from. Queued by is one of Sequence (a campaign), AI agent, Chat, Telegram bot, Survey, API or Manual.

Narrow the list with Search recipient or message, All channels, All sources and All accounts, or click Clear filters.

These actions apply to Telegram messages:

  1. Open the row’s Actions menu.
  2. Pick Send now to move a message scheduled for later to the front of the queue.
  3. Pick Retry on a failed message to queue it again with a fresh set of attempts.
  4. Pick Cancel to remove a queued message before it goes out.

For many messages at once, use Cancel everything queued in the Queued view, or the retry button in the Failed view (for example Retry 5 failed). Bulk retry covers failures from the last 7 days.

Campaign steps on email, X and social have no row actions. To hold them back, pause the campaign in Campaigns.

Pinlyx retries temporary problems on its own, so a failed row usually means retrying will not help yet.

  • Connection, proxy and session problems on Telegram are retried up to 3 times, with a longer wait each time. The row shows which attempt it is on.
  • Telegram asking you to slow down (a flood wait) is not counted as an error. The message waits as long as Telegram asks, plus 30 seconds, and is tried again, up to 10 times.
  • Permanent problems fail at once with the reason: the recipient blocked you or restricts messages, the username does not exist, the message is empty or too long, or the sending account is not verified.
  • Campaign steps on email, X and social are retried by the campaign. See Campaigns.

Messages with a later send time wait in Queued under Today, Tomorrow or Later. Campaigns schedule their own steps from your delays and sending window. Through the API you can queue a Telegram message for a set time with runAt: see Send a Telegram message.

When a Telegram account has to wait before it may send again, a notice at the top of the page names it. Its messages stay in the queue and go out when the account is free again, nothing is lost. The limits behind this, and how campaigns spread sends over the day, are explained in Safe sending limits.

  • Messages only leave from accounts that are connected and verified. A message for an account that is disconnected waits in the queue until the account is back.
  • Cancelling a queued message deletes it. It does not appear in history.
  • Your plan does not cap how many messages you send a day. Pacing comes from the per-account limits and your campaign settings.

Check the Queued view for the next send time and the notice at the top for accounts that are waiting. Then check that the sending account is still connected in Accounts. More fixes in Troubleshooting.

This usually has one cause, such as an expired session or a proxy that stopped working. Fix the account, then use Retry in the Failed view to queue them all again.