Why a post failed to publish

A failed post keeps its reason and can be retried from the calendar. Find the reason first: retrying without fixing the cause just fails again.

The account is no longer connected

The most common cause. A token could not be renewed, usually because the social account's password changed or access was revoked on the platform's side.

Fix: reconnect from Connected accounts, then retry the post.

The platform is not on your plan

Your plan does not include publishing to that network.

Fix: upgrade, or publish that one manually.

The platform has no live integration

The network is marked coming soon: content is written for it, but nothing can send to it.

Fix: copy the caption out and post it yourself. See platform support.

The platform rejected it

The network accepted the request and refused the content. Usual causes: media in a format or aspect ratio it will not take, a caption over the length limit, or a post shape the platform does not support for that account type.

Fix: edit the post to match what the platform accepts, then retry.

The media could not be fetched

Some platforms fetch your image or video from a URL rather than receiving an upload. If that fetch fails, the post fails.

Fix: retry. If it persists, re-upload the media on the post.

Rate limited

Too many sends in too short a window, either from us or from other tools using the same account.

Fix: retry later. If this is routine, you are scheduling more densely than the account can carry.

It is not failed, it is held

A post sitting past its time in pending review is waiting on a client decision, not broken. See client approvals.

A post sitting as scheduled a minute or two past its time is normal: the worker runs on an interval and drains oldest first.

Nothing here matches

Get in touch with the post's exact failure message. That string is what identifies the cause.