Automatic channel recovery
Understand how BlendDuck refreshes social credentials and recovers unavailable connections.
- Documentation owner:
- BlendDuck Documentation
- Last reviewed:
BlendDuck owns the social-channel credential lifecycle. Access-token expiry, refresh timing, and recovery state are internal operations rather than user actions.
Before you start
No action is needed for ordinary token expiry. If a provider authorization or native account role changed, confirm the intended Page, profile, channel, organization, or location still exists before using Connect Channel again.
What happens automatically
- A usable refresh grant renews the access token when provider work needs it.
- Expiring and refresh-due states stay out of the Channels interface.
- Provider retries remain bounded and idempotent, so recovery cannot create a duplicate post.
- A connection that cannot currently publish is excluded from new publishing until its provider access is usable again.
When provider authorization changed
If the provider revoked the app, removed the account role, or requires newly approved permissions, use the existing Connect Channel flow. BlendDuck matches the returned native identity to the saved channel where supported; it does not expose a separate reconnect operation.
Before connecting again, sign in to the intended native account and confirm its Page, profile, channel, organization, or location still exists. For Bluesky or Telegram, rotate a compromised App Password or bot token on the provider before entering the replacement through the normal connection dialog.
Failed and scheduled posts
Connection recovery does not automatically publish an old failed target. Scheduled work keeps its original channel and timing, while failed targets stay visible in Publishing issues for an explicit retry after the connection is available. Permanent validation failures still require editing the post.
What users see
Channels show publishing-relevant states such as connected, paused, setup required, or temporarily unavailable. Token expiry, refresh timing, missing refresh credentials, and internal recovery controls are not presented as user tasks.
You are done when
- Channels shows no token-expiry, refresh-due, or reconnect control.
- Available channels can publish through their original native identity.
- Failed targets remain unpublished until explicitly retried.
If something blocks you
| Symptom | Safe next step |
|---|---|
| The provider selects the wrong identity | Cancel the provider flow, sign in to the intended native account, then use Connect Channel again. |
| The native Page, organization, or location is missing | Restore the required native account role before connecting. |
| A failed target remains unavailable | Keep it unpublished and inspect the saved provider error; validation failures require an edit. |
| An App Password or bot token was exposed | Rotate it on the provider, then enter the replacement through the normal connection dialog. |