Platform limits & publishing queues
Your plan sets the pace of publishing across your account. Provider limits apply to their documented account, destination or application scope.
Publishing pace by plan
These allowances are shared across all workspaces owned by the billing account. They include dashboard, API, bulk, scheduled, recurring, and automation submissions.
| Plan | Active destinations | Starts per minute |
|---|---|---|
| Pro | 4 | 120 |
| Legacy paid plans | 2 | 30 |
| Lifetime deals (LTD) | 3 | 30 |
Pro has the highest queue preference, followed by legacy paid plans and LTD. Publishing requires a current trial, subscription or eligible lifetime purchase. Accounts with ended trials or subscriptions need activation or billing recovery. Legacy Basic and Team purchases retain their existing allowances. Limits are maximum allowances, not guaranteed delivery speeds.
Recurring publishing
There are no plan-based quotas on active recurring posts or daily, weekly, monthly or yearly recurring schedules. Keep the schedules you need and pause or resume them whenever you choose.
Scheduled runs join the publishing queue automatically. Publishing pace, provider limits, platform rules, connection permissions and billing access still apply.
If a channel fails 5 recurring runs in a row because of a connection or permission problem, Postly temporarily holds recurring publishing to that channel only. Reconnecting resumes it, and we also try again after 3 days. Other channels keep publishing.
What do these terms mean?
- Active destinations
- How many destination publishing jobs your account can run at the same time. One post sent to Facebook, Instagram, and LinkedIn creates 3 jobs. LTD can run up to three at a time; Pro can run up to four, subject to publishing capacity and platform restrictions. This does not limit how many channels you can connect.
- Starts per minute
- How many destination jobs can begin in any rolling 60 seconds. LTD allows up to 30 starts, with up to 3 active jobs at a time. Even if all thirty finish quickly, the 31st waits for allowance to return. Starting a job does not mean it has published successfully. Retrying a failed publication can use another start.
Why is my post waiting?
One post sent to 53 channels creates 53 destination jobs. When your account reaches its active-job or per-minute allowance, the remaining jobs stay safely queued and start automatically as capacity becomes available. Do not resubmit queued content.
- Queued
- Waiting for account allowance, a publishing slot, or its scheduled time. Normal plan batching needs no action.
- Publishing
- Postly is working on the destination; the platform may still be processing it.
- Checking allowance
- If Postly’s allowance check is temporarily unavailable, queued jobs retry automatically before sending. After repeated unsuccessful checks, open the failed post to review and retry.
- Platform limit reached or failed
- Open the post for its reset time, connection or platform error, and recovery steps. You may need to reschedule or retry after allowance returns.
- Unconfirmed
- Check the destination before retrying to avoid a duplicate publication.
In Home or Posts, open Publishing queue for per-destination progress, submission source, and next eligible time. API submissions appear there too. Next eligible is the earliest retry time, not a promised completion time.
Provider publishing limits
Postly does not impose a blanket daily publishing cap. Each platform sets its own API and account limits. These can vary by destination, content type, application and account permissions.
Postly uses the allowance reported by the provider or verified for its application. When no cap is available, Postly applies no numeric publishing cap of its own. Missing quota data does not mean zero or unlimited capacity. Publishing is paced through the queue to protect your accounts and keep service reliable.
If a verified provider allowance is exhausted, the affected publication is not sent. Your content stays saved for editing, rescheduling or retrying after the provider allowance returns.
Connections that need attention
Home’s Needs attention list shows each expired or expiring connection. For supported connections with a known expiry date, Postly issues email and dashboard warnings at 7 and 2 days. Platforms can also revoke access without advance notice.
How to resolve connection and Telegram permission errors
Open Social accounts and reconnect the account that manages the destination, granting publishing permissions. For Facebook, select the affected Page; if Facebook requests identity confirmation, complete it in the Facebook app. Reconnecting does not automatically resend failed posts.
For Telegram, add the bot selected in Postly as an administrator of the group or channel with permission to post messages and media, including photos. Postly checks the selected bot’s rights, but only a Telegram administrator can grant them.
Bulk uploads and Google Sheets
Before saving new import rows, Postly checks the selected connections, Telegram bot permissions, and any known provider allowance. If a check fails, fix the reported issue and retry the import; no new rows are scheduled.
Spread large imports across later dates. Checks cover the new rows together and current allowance for Publish now. Future scheduling does not reserve allowance: existing schedules, other submissions, and later connection changes can affect publishing. The final check always runs before sending. API imports use the same checks and appear in your dashboard queue.
Platform details
Expand a platform for its limit source and references. A missing provider cap means Postly applies no numeric cap of its own. Platform permissions, media requirements, and restrictions can also affect publishing.
Loading platform rules…