Channel health and reconnecting
Every channel shows a health state — healthy channels publish silently, expired ones need reconnecting, and degraded ones warn you about recent failures.
Every connected channel carries a health state so you always know whether it can publish. A healthy channel is invisible — it just works. A channel whose token has expired or been revoked wears a needs reconnect badge and stops publishing until you re-authorize, and a channel with several recent publish failures wears a softer recent failures warning while still working. Both surface on the channel’s card under Settings → Social Profiles.
The three states
| State | Badge | What it means |
|---|---|---|
| Healthy | none | The channel is authorized and publishing normally. |
| Degraded | recent failures (amber) | Publishing still works, but the channel has failed several times recently. |
| Needs reconnect | needs reconnect (red) | The channel’s authorization is expired or revoked; publishing is blocked until you reconnect. |
A healthy channel shows no badge and needs no attention. A degraded channel shows the amber “recent failures” warning — it is non-blocking, a heads-up that something has been going wrong (rate limits, transient platform errors) so you can look before it becomes a hard failure. A needs reconnect channel shows the red badge and a Reconnect button; it cannot publish until you re-authorize.
Why channels expire
Social networks issue access tokens that don’t last forever, and a channel goes into the needs-reconnect state whenever its authorization can no longer be used. Common causes:
- The token expired and could not be refreshed. LinkedIn tokens last 60 days; Instagram and Facebook issue long-lived tokens of about 60 days with no refresh token, so they must be renewed by reconnecting.
- You revoked access to Inklate from the network’s own app settings.
- The network invalidated the token — for example after a password change or a permissions change on the account.
X is the exception that self-heals most often: it issues a refresh token, so Inklate keeps the connection alive on its own until the refresh itself is rejected.
Reconnecting a channel
Reconnecting re-runs the same OAuth authorization you did when you first connected — you never type a social password into Inklate. From the channel’s card:
- Click Reconnect on the channel showing the red badge.
- Approve the permissions again on the network’s consent screen and return.
- Inklate restores the same channel with a fresh token. Your published history, scheduled posts, and analytics are all preserved.
Because reconnecting targets the same destination, you don’t lose anything — the channel picks up exactly where it left off. Any posts scheduled while the channel was expired simply publish once it’s healthy again.
What happens to scheduled posts
An expired channel does not silently drop your work. Each channel publishes independently, so one expired channel never blocks the others in the same post — see Publishing for how per-channel publishing and failures are handled. If you fully disconnect a channel rather than reconnect it, its scheduled posts return to drafts and its published history is kept, so nothing is lost and re-picking the destination later revives it.
Connect the Facebook pages you manage, then publish text and photo posts, video posts, reels, and stories — each authored as the page itself.
A tour of the composer
The composer is one screen where you write a post once and adapt it per channel — a Base tab, per-channel tabs with native previews, a sync bar, and a rail.