The smart queue & auto-retry

When a send can’t go out safely right now — a rate ceiling, warming, night pause, or a high risk score — what happens depends on your tier. On Pro it’s handled for you; this is a real reason to upgrade if you automate at volume.

Free vs Pro behaviour

• Free: a blocked send returns a clear error — 429 Too Many Requests over the API, or a surfaced error in the app — with the reason and a retry hint. Your code (or you) back off and retry. It is never silently parked.
• Pro: the smart queue accepts the send, holds it, and retries automatically when there’s headroom — so your automation doesn’t have to babysit limits.

Priority — the important ones go first

Every queued item carries a priority from 0 (most urgent) to 3 (lowest), default 2. When work backs up, the queue always sends the lowest number first, so an OTP or order confirmation (priority: 0) jumps ahead of a low-priority notification batch (priority: 3). Set it on the send or enqueue call; items at the same priority go oldest-first.

Risk pauses resume automatically

If a send is held because risk got too high, the account auto-cools — and the queue drains itself the moment your risk score recovers to a safe level (it isn’t a fixed wait). You don’t have to retry or un-pause anything; held items simply start flowing again once it’s safe.

Still stuck — open a ticket · Back to all articles