Troubleshooting
Most problems in Postbean come down to a token the network no longer accepts. The fix is almost always the same: reconnect the channel.
Start here
Section titled “Start here”A channel marked “needs reconnecting” — a token expired, or you revoked Postbean’s access on the network. The channel stays in your list rather than disappearing, so nothing scheduled to it is lost. Open Connections, click Reconnect on that channel and sign in again. Anything still queued goes out normally afterwards.
A post that failed on one network — the other networks are unaffected. Open the post from Post or Publish → Queue and check the message on the failed network; it comes from the platform and usually says exactly what it objected to.
By symptom
Section titled “By symptom”- I cannot sign in
- Instagram: connection and posting problems
- Instagram: “400 session invalid”
- Facebook Pages: connection problems
- YouTube: “insufficient permissions”
Scheduled posts that did not go out
Section titled “Scheduled posts that did not go out”Scheduled posts are dispatched by a worker on the server, so closing your browser is not the cause. Check, in this order:
- The post is in Publish → Queue and not in Drafts — a draft has no date and never publishes on its own.
- The scheduled time, in your workspace timezone. The calendar shows which one is in effect; it is set in Settings → Workspace.
- The channel is not marked as needing to be reconnected.
- The post’s own detail view, for a per-network error message.
Still stuck
Section titled “Still stuck”Write to support@postbean.app with the post’s link and the error text as it appears in Postbean. The platform’s own wording is what makes these quick to diagnose.