Why a post failed, and how to retry it

A post that goes to six accounts has six outcomes, not one. Schedchie records and shows every one of them, which is why a post can be live on four platforms and still tell you something went wrong.

What the five statuses mean

You can filter the list view by status, which is the fastest way to answer "did everything go out this week".

Reading the per-account result

Open the post. Two places carry the detail:

• Publishing To lists every account with a green tick or a red cross, so you can see at a glance which ones landed.
• What happened appears on anything that failed, and gives the reason per account, in the platform's own words, cleaned up.

A row prefixed Skipped: was never attempted. That means the account was already flagged as needing attention before publish time, so the post was not thrown at a connection that could not take it.

Retrying

Failed and partially-failed posts both carry a retry control. On a partial post it reads Retry failed accounts, and it means exactly that: the accounts that already published are left alone, so nothing gets posted twice.

• Retry runs immediately by default — you do not have to pick a new time.
• You can retry as many times as you like.
• Rescheduling a failed post also re-queues it, for the new time.
• Your content and media are still attached; nothing needs re-uploading.

If your posts need a workspace owner's approval, a retry goes back to them for approval rather than straight to the queue. See team members and approvals.

The email you get

When a post does not fully go out, an email tells you so. The subject says which way it went — published to some accounts, or to none — and the body lists each account that missed, with the reason.

• The button in it opens that exact post in your dashboard, where retry is one click.
• One email per affected post, and at most one of these per hour. Every affected post is in the dashboard regardless.
• You can switch these off in Dashboard → Settings if you would rather check the calendar yourself.

Common reasons, and what to do

What already happened automatically

By the time you see a failure, several things have been tried:

• Media is verified to exist in storage before any publish attempt, so a post is not sent at a platform with a missing file.
• Rate limits, timeouts and platform 5xx errors are retried automatically with a growing gap between attempts. Most of these never reach you.
• Errors that will not improve on their own — a lapsed token, a missing permission, an empty X batch — are not retried in a loop. They are surfaced instead, because they need you.
• Connections are checked and refreshed daily, so "the token quietly expired" is caught before a post is due rather than after.

Still not clear?

Send the post's scheduled time and the account name to support and you get the publish log for it. The status page publishes a real post every hour and shows the result, so you can also check whether a platform is having a wider moment.