A channel stopped working
What 'Waiting on reconnect' means, why your scheduled posts were parked rather than failed, and how reconnecting restores the whole queue.
Every social network expires the access it grants an app. Change your password, revoke access, lose admin rights on a Page, or simply wait long enough, and the connection stops working. PostDaily tries to renew connections automatically in the background, so most of the time you never see this. When renewal genuinely fails, the channel is marked as needing reconnection.
Your scheduled posts were parked, not lost
This is the part worth knowing. When a channel breaks, every post already queued behind it is moved to Waiting on reconnect rather than being attempted and failed. Nothing was sent, nothing is wrong with the posts, and you do not get a failure email for each one.
The alternative — which is what most schedulers do — is to let the queue run into the broken connection and fail one post at a time, at each scheduled slot, generating a notification for every one. You would come back to a column of failures and no queue left.
Reconnect the channel
- 1Open Channels
The channel needing attention is flagged in the list.
- 2Choose Reconnect
You are sent to the network's own authorization screen, exactly as when you first connected.
- 3Approve the same permissions
Approve every permission requested. Declining one silently removes a capability — first comments or analytics usually — and the channel will look connected while quietly failing at that one thing.
- 4Check the queue
Parked posts flip back to Scheduled. Anything whose slot passed while the channel was broken stays parked so it does not publish unexpectedly late — reschedule those yourself.
If it breaks again immediately
A channel that needs reconnecting again within minutes usually means the underlying access is being revoked, not expiring. The common causes:
- You lost admin rights on the Facebook Page or the account. Access follows your role — if someone removed it, reconnecting cannot restore it.
- The password changed on the network account. Some networks invalidate every app authorization when that happens.
- An app password was revoked. For Bluesky, check the app password you used still exists in Bluesky's settings.
- Someone removed the app in the network's connected-apps or business-integrations settings.
One transient error from a network does not mark a channel as broken — it takes repeated failures, so a momentary outage on their side will not disconnect you.