This is the failure mode that makes people abandon a scheduler, and it happens without a single error appearing anywhere they look.
How the tokens work
When you connect a Meta account, the app receives a short-lived token and exchanges it for a long-lived one. Long-lived sounds permanent. It means roughly 60 days.
After that the token stops working. Your posts stay in the calendar, marked and waiting. They simply never leave.
The part that is easy to get wrong
Page access tokens derived from a long-lived user token do not expire on a clock at all — they stop working when access is revoked. Stamping a 60-day expiry on them produces a reconnect warning every two months on accounts that are working perfectly, which teaches people to dismiss warnings.
So the honest model is: warn on a real expiry date when the platform gave you one, and catch revocation through the publish failure, because that is the only signal that exists.
What a tool owes you
- A visible warning before the token dies, not after
- The warning where you will see it — not buried in a settings page you visit twice a year
- A one-click reconnect, because the fix is trivial once you know
A week's notice turns a silent outage into a thirty-second task.