Disconnecting a channel
Disconnecting removes a channel from Schedulin. The channel's published history stays in your analytics, but Schedulin stops being able to publish or read new data from it.
How to disconnect
- Open the Channels page.
- Click the channel you want to remove.
- Click Disconnect.
- Confirm. The channel is removed from any active queues immediately.
You can also revoke Schedulin's access directly from the social network's settings (e.g. Meta's Business Settings, X's Connected Apps). When you do that, Schedulin detects the revocation on the next API call and the channel moves to a needs-refresh state — at which point you can disconnect cleanly from the Channels page.
What happens to scheduled posts
When you disconnect a channel, any future scheduled posts on that channel are cancelled. They stay visible in the calendar as cancelled drafts so you can copy the content to another channel, but they will not publish.
If a post was scheduled to multiple channels, the post still publishes to the channels that remain connected — only the disconnected channel is dropped.
What happens to analytics
Historical analytics for posts already published are preserved. You can still see metrics for everything the channel published while it was connected.
New metrics stop coming in once the channel is disconnected, since Schedulin no longer has API access.
Reconnecting later
You can reconnect the same account at any time. Schedulin keeps the channel's history under the hood, so reconnecting restores:
- All historical posts and analytics
- The channel's posting schedule
- Any tags or labels you'd applied to its content
What it does not restore is the cancelled scheduled posts — those need to be re-created.
Disconnecting vs. just pausing
If you only want to stop publishing temporarily (e.g. during a quiet period), it's usually better to pause the queue on that channel rather than disconnect. Pausing keeps the token alive and your queue intact; disconnecting cancels everything.