Keeping your channels healthy

Most "why didn't this post?" issues come from a small set of root causes that are easy to prevent.

Reconnect quarterly

Some networks rotate their OAuth requirements once or twice a year. Doing a fresh reconnect every 3 months catches stale tokens before they break at the worst moment.

Put a recurring reminder on your calendar: Reconnect Schedulin channels.

Don't share passwords

If multiple team members log into the underlying social account from different IPs, networks often trigger "suspicious activity" lockouts. The lockout revokes Schedulin's token. Avoid this by:

Using the social network's official team-member features (Meta Business Manager, LinkedIn Page admins).
Adding teammates to your Schedulin workspace instead of sharing the social-account password.

Watch for the warning badge

The Channels page shows a yellow badge the moment a channel needs attention. Fix it the same day if you can — every queued post on that channel is paused until reconnected.

Stay within rate limits

Network rate limits exist (see Daily posting limits) and your queue respects them. If you regularly hit them, you're either:

Running an automation that's too aggressive — throttle it.
On a too-small plan — upgrade for higher monthly post caps.

Diversify auth

For Meta especially, the connecting Facebook user matters. If that user leaves the company or removes themselves as a Page admin, the token dies. Best practice: