A channel shows as disconnected
Why a connected channel goes red, and the safest way to reconnect without losing scheduled posts.
A channel turns red when Unison can no longer call its API on your behalf. The most common cause is an expired or revoked token, but it is rarely a real failure: reconnecting takes thirty seconds and your scheduled posts stay where they are.
Why it happens
- You revoked the app at the network. If you removed Unison from your
Meta, Google, X, or Pinterest app permissions page, the next API call
fails with
401 Unauthorized. - The token expired. Some networks issue short-lived refresh tokens that need re-consent every 60 to 90 days. We refresh in the background but a network policy change can invalidate a refresh token.
- You changed your password at the network. On networks where Unison uses an app password (Bluesky, Mastodon) the token can be invalidated by a password change.
- Your account was restricted at the network. If a network restricts or suspends your account, our calls fail with a network-side error message.
How to reconnect
- 1
Open Settings → Channels. The disconnected channel shows a red dot and a Reconnect button.
- 2
Click Reconnect and run through the OAuth flow again. For Bluesky, Mastodon, and Telegram, paste the new app password or bot token instead.
- 3
Once the green dot returns, every scheduled post for that channel will fire on its original timestamp.
What happens to in-flight posts
Posts scheduled for a disconnected channel are put on hold, not deleted. You can see them in the queue with a Channel disconnected badge. Reconnecting unblocks them automatically.
If you want to abandon them, open the queue and bulk-delete the held posts.
Still not working
If reconnecting fails repeatedly, check:
- The network's status page for an outage.
- Whether the connecting account has the required role on the Page, Channel, or Group you are publishing to.
- Whether your network account has been restricted (most networks email you when this happens).
If none of those apply, drop us a line at hello@unison.ink with the channel name and the timestamp of the most recent failure and we will investigate.
Was this helpful?