Move a post that failed
A failed post always carries one reason and one next step. Read the reason, do the one thing it asks, then retry the post or schedule it again. Retrying is safe, and it only resends what did not go out.
The NioConnect team3 min readOn this page
- Time
- About 3 minutes
- You need
- A post marked as failed
- Where
- Calendar or Posts
Before you start
Open the failed post from the calendar or the Posts list. The reason is written in plain words next to each channel that failed, and it names who can fix it.
Read the reason and act
- Read the reason shown on the failed channel.
- Do the one thing it asks, using the table below.
- Press Retry to send the failed channels again, or edit the post and schedule it again where the reason says so.
- Watch the calendar until the status changes to published.
| What happened | What to do | Who can do it |
|---|---|---|
| The channel access had expired | Reconnect the channel, then retry | Owner or Admin |
| The channel was switched off | Turn it back on, then retry | Owner or Admin |
| The channel was disconnected | Connect the account again, then schedule the post to it | Owner or Admin |
| The platform would not accept the post as written | Edit it for that platform and schedule it again | Anyone who edits posts |
| The media could not be prepared | Replace the file and schedule again | Anyone who edits posts |
| The platform refused or could not take it just then | Retry | Anyone who edits posts |
| The plan limit or a failed payment | Change the plan or fix billing | Owner |
What you should see
Retry sends only the channels that failed. A thread that stopped partway shows how far it got, for example published 2 of 5 parts, and retry carries on from the next part without repeating the ones already out.
A disconnected channel is a retired connection, so retrying cannot help. Reconnecting makes a new channel, and the post has to be scheduled to it.
A platform asking NioConnect to slow down is not a failure at all. The post waits its turn and goes out on its own.
Why retrying is safe
Each publish carries a key made before the platform is called, and the platform is checked before anything is sent again. The post on publish once explains this and is honest about what platforms allow.
Changing the time, or posting again
To move a post that has not gone out, open it and change the time in the editor. If a post already published and you want it out again, saving offers a choice: correct the record, or publish it again as a new post with its own key. Pick deliberately; they are different things.
The reasons in full are in the help article Why a post failed.
Retrying content a platform has refused only repeats the refusal. Edit first, then schedule again.
If something goes wrong
Some posts did not go out and are still not failures. A post can be held while an emergency stop is on, while it waits for approval, or while its channel is switched off after a plan change. A hold lets the post publish once the cause is gone, and a post whose time passed during an emergency stop is held rather than published late, so you decide what to do with it.
Reconnecting and switching channels back on are for an Owner or Admin, billing is for an Owner, and editing and retrying are for the people who write posts. If the button is not yours, the reason says who to ask.
If a reason says something went wrong on our side, the post is held rather than published incomplete, and retry sends it again. If you cannot reconnect or switch a channel, ask an Owner or Admin; the reason names who can.
Check your result
- Confirm the reason on the failed channel and who it names.
- Fix that one cause before retrying.
- Check that the calendar shows published once the platform confirms.
- Verify the post appears only once on the platform.
Written by The NioConnect team.
Posts that say why they failed, on one calendar.
Start 7-day trial