Daily post limits & publishing queues
Your plan sets the pace of publishing across your account. Daily limits apply separately to each connected destination.
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 post limits
To manage system constraints and keep publishing fair for every account, each plan has a limit on recurring posts. Limits are shared across all workspaces owned by the billing account.
| Plan | Daily | Weekly | Monthly | Total active |
|---|---|---|---|---|
| Pro | 250 | 1,000 | 4,000 | 25,000 |
| LTD Upgrade | 50 | 250 | 1,500 | 10,000 |
| Lifetime deals (LTD) | 20 | 100 | 600 | 5,000 |
| Legacy paid plans | 20 | 100 | 600 | 5,000 |
- How posts are counted
- Each active recurring post counts once toward the allowance for how often it actually repeats, no matter how many channels it is sent to. Daily covers posts that repeat at least once a day, including hourly. Weekly covers every 7 to 27 days, and monthly covers every 28 to 364 days. Posts that repeat yearly or less often count only toward the total.
- Every scheduled run publishes
- Limits are checked when you create, edit or resume a recurring post. Once a post is active, each of its scheduled runs is published. There is no daily cap on runs.
- Above the active limit
- Recurring posts above your plan’s total limit are paused, starting with the most recently created, and we email you. Your oldest recurring posts keep running. Nothing is deleted: the posts and their schedules stay saved.
- Channels that keep failing
- If a channel fails 5 recurring runs in a row because of a connection or permission problem, Postly pauses recurring publishing to that channel only and emails you. Your other channels keep publishing. Reconnecting the account resumes it, and we also try again after 3 days.
- Resuming paused posts
- Pause or delete recurring posts you no longer need, or change how often a post repeats, then resume the ones you want to keep running.
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 two 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 2 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.
- Daily 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.
Daily destination limits
Each connected destination has a Postly safety limit of 100 publishing operations in a rolling 24-hour window. Lower or more restrictive platform limits still apply.
This daily limit is separate from your account’s publishing pace. Both apply, including on plans with unlimited scheduling. Windows move continuously; they do not reset at midnight or on the minute.
If a known daily allowance is exhausted, Postly stops the affected operation before sending it. Your content stays saved for editing, rescheduling, or retrying after 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 daily publishing volume. 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 current rules and references. Platform permissions, media requirements, and restrictions can also affect publishing.
Loading platform rules…