Fix a post that failed to publish
How to find a failed post, read why each channel failed, and use the one next step Publedia offers for it, from reconnecting to editing or retrying.
A post goes to each of its channels separately, so it can publish on four networks and fail on a fifth. When that happens, the post records which channel failed, why, and what you can do about it. Your text and media are kept, so fixing a failure never means writing the post again.
Find failed posts
- Home leads with the posts that need a decision, failed ones included.
- The notifications bell lists failed posts along with channels that need reconnecting.
- Posts can be filtered by status: choose Failed to see every post with a failed channel.
Open the post to see its detail page, with one row per channel.
Read what happened
Each failed channel's row says why it failed, in one of these kinds:
| Shown as | What it means | Next step offered |
|---|---|---|
| Authorization | The network no longer accepts Publedia's access to the account | Reconnect channel |
| Not permitted | The network refused the account itself, for example a missing Page role or a restricted account | Check channel |
| Plan limit reached | Your plan's allowance stopped it; the post never left Publedia | Upgrade plan |
| Rejected by the platform | The network refused this post: too long, a file it does not accept, or similar | Edit post |
| Blocked by platform rules | The network's rules stopped the content | Edit post |
| Rate limited, Timed out, Platform unavailable | A temporary problem on the network's side | Retry |
| Not found, Unreadable response, Unknown | Something went wrong that sending again usually fixes | Retry |
The row shows the one step most likely to fix the failure. Retry stays available in the row's menu for when you have sorted out the cause another way.
Fix it
Reconnect
Select Reconnect channel, sign in on the network's screen, then come back to the post and select Retry. See reconnecting a channel.
Check the channel
The network refused the account: for example, you no longer manage the Facebook Page, or the account is restricted. Sending again gets the same answer until that changes on the network, so fix it there first, then retry.
Edit the post
Select Edit post to open it in the composer. The network's reason tells you what to change: shorten the text, swap a file, or remove something the network does not accept. Check that channel's counter and preview, then save.
Upgrade or wait
A plan limit stopped the post before it reached the network. On X this is usually the monthly X allowance, which is checked again at the moment a post is sent and resets on the first day of each calendar month, in UTC. Either wait for the reset and retry, or ask an admin to change plan in Settings, Plan and usage. A workspace that connects its own X developer app is not limited by the X allowance.
Retry
For temporary problems, select Retry. Publedia only resends to the channels that failed; channels that already published are not posted to again. If retry cannot send to a channel, it tells you which one and why.
Retrying safely
A timeout is the awkward case: the network may or may not have received the first attempt. On X, LinkedIn, YouTube and Bluesky, if Publedia cannot confirm whether a send went out, it does not send again and asks you to check instead: the post says it couldn't confirm whether the post went out, so it wasn't sent again. After any timeout, on any network, check the account on the network before you select Retry, because a retry you start is a new attempt.
Prevent the common failures
- Reconnect channels marked "Expiring soon" before they lapse, especially LinkedIn every 60 days.
- Check each channel's counter and preview before scheduling. Most rejections are text that is too long or media a network does not accept.
- Keep video within each network's length limit. The supported platforms page lists them.
- Watch your plan's allowances before a busy week. An admin can see them in Settings, Plan and usage.
Still stuck?
If a post keeps failing after you have tried the step shown, contact us with the post and the time it was scheduled for, and we will look at the network's response.