Check a scheduled post that did not publish
Open the post in Calendar and inspect each platform's delivery status before retrying anything. A post missing from one account may already be live on another. Recreating the whole post can produce duplicates where delivery succeeded.
First establish what has happened
Check the scheduled date and time, the destination account, and the status for each platform. If you are looking at a pending draft in Approvals, it has not followed the same path as an approved post that failed during delivery.
| What you find | What to do next |
|---|---|
| A future scheduled time | Wait for that time, or deliberately change your publishing plan. It is not yet a missed delivery. |
| A platform marked published | Check that destination account before posting another copy. |
| A platform with a delivery error | Read the error, fix its cause, then retry that platform if the action is available. |
| A platform still pending or processing | Do not assume it failed. Check again before making a new submission. |
| Different results across platforms | Handle the failed destination separately. Leave successful deliveries alone. |
If the displayed status and the destination account disagree, record both. Avoid a second submission while you are unsure whether the first reached the platform.
Fix the cause before using Retry
For a failed platform, the post details show its error and a Retry action when available.
A disconnected or paused account needs attention in Connections first. Reconnect the affected account or unpause it if you intend publishing to resume. Be careful with account identity: a retry that asks for the original upload account needs that account, not another profile on the same network.
Other errors can concern publishing availability or requirements of the destination platform. Follow the specific message rather than repeatedly clicking Retry. If your free publishing window has ended, continuing automated publishing requires a paid plan; the pricing page explains the current options.
Also check whether the post is still appropriate. A service announcement that was useful yesterday may be misleading today. Fixing a connection is not a reason to send stale content.
Retry the affected platform and verify the result
Once you have addressed the cause, return to the post in Calendar and choose Retry beside the failed platform.
The retry requests another attempt or a continuation of the platform's delivery process. It does not mean the post has already published. Check the status again, then verify the result on the destination account.
Do not create a new all-platform post while that attempt is in progress. If only one platform failed, a new all-platform post risks repeating the content everywhere else. If the same error returns, stop and investigate that error instead of making repeated submissions.
For an upload that is already underway, the platform may still be processing or confirming it. Let the existing attempt resolve before starting a replacement. A delayed confirmation and a rejected upload are different problems.
A failed draft needs a different retry
A Retry control in the Approvals progress display concerns preparation, such as a failed draft or media stage. A Retry next to a platform in Calendar concerns delivery.
Use the location and error to identify which problem you have. Regenerating media does not reconnect an account, and retrying delivery does not repair an unfinished draft.
If the post is still unresolved
Keep a short record for troubleshooting:
- The post title and scheduled time, including your time zone.
- The affected platform and destination account.
- The exact error and whether other platforms succeeded.
- What you changed and when you last retried.
- Whether a copy is visible on the destination platform.
Do not include passwords or access tokens. This record makes it possible to investigate the existing attempt before anyone suggests a replacement post.