logo
Schedulin

Refreshing a channel

Every social network issues access tokens that eventually expire or get revoked. When this happens to one of your channels, Schedulin marks it as needing a refresh and pauses publishing on it until you reconnect.

Why channels need refreshing

Common reasons:

  • The token expired (Meta's long-lived tokens last ~60 days; we refresh them automatically, but a refresh can fail if you changed passwords).
  • You changed your account password on the network.
  • You revoked Schedulin's access from the network's settings page.
  • The network changed its required permissions and we need you to re-approve.

How you'll know

Channels that need a refresh show a yellow warning badge on the Channels page and in the post composer. Scheduled posts on that channel won't publish — they stay queued and you'll see a banner explaining the issue.

We also email the workspace owner when a channel first enters the needs-refresh state, so you don't have to be watching the dashboard.

How to refresh

  1. Open the Channels page.
  2. Click the channel with the warning badge.
  3. Click Reconnect. You'll be sent through the same OAuth flow as the original connection.
  4. Sign in with the same account and approve the permissions.

When you return to Schedulin, the channel is active again and any posts that were queued during the outage publish at their next scheduled time (or immediately if they're already past due).

Your scheduled posts are safe

Refreshing a channel does not delete drafts, scheduled posts, or analytics. The channel's identity stays the same — only the underlying token changes.

If you reconnect a different account by mistake (e.g. you signed into a personal IG instead of the business one), the channel switches to the new account. Disconnect and reconnect to fix.

Channels that won't refresh

If reconnect keeps failing:

  • Two-factor recovery on the social network — if the social network requires 2FA, make sure you can complete it. Some flows require the network's mobile app.
  • Removed admin access — for Facebook Pages and LinkedIn company pages, you need to still be an admin of the underlying asset.
  • Account suspended — if the network suspended the account, the OAuth flow will fail. Resolve the suspension on the network's side first.

See also