Why a Facebook Page API connection stops working, and how to keep it alive
A Facebook Page connection stops working when Meta stops accepting its token or stops sending its events: the token came from a short-lived sign-in, the person changed their password (error 190, subcode 460), lost their role on the Page (492) or removed the app under Business Integrations (458), a permission went unused for 90 days, the app sat inactive, or Meta restricted the Page.
easyCoexistence takes each Page's token from a long-lived sign-in, checks the Page every 6 hours and emails you when Meta refuses the token, and one Facebook sign-in brings the Page back as the same connection, with its comment rules and automations.
Lifetime of Meta's default user and Page tokens; a Page token from a long-lived user token has no expiration date.
With no logins, API calls or webhooks for this long, Meta deems an app inactive and invalidates all its tokens.
Page permissions such as pages_manage_posts and read_insights do not expire with the 90-day data access period.
The Page Integrity restriction that blocks a Page from sending messages through the Messenger Platform API.
How often easyCoexistence checks each connected Page with a light Graph call, emailing the owner if Meta refuses the token.
What can make a Page connection stop working?
Causes on four levels: the person's sign-in, the app's permissions and standing, the Page itself, and the webhook subscription. Each one shows up in its own way, and most come back as error 190 with a subcode that names the cause:
Why would a Page token expire within hours?
Because it was read from /me/accounts with a short-lived user token, and then it is short-lived too. Meta's default user and Page tokens expire within hours, about one to two for a short-lived token. Exchanged on the server with fb_exchange_token, the user token lasts about 60 days, and a Page token read with it has no expiration date. Meta will not extend a token that has already expired: the error reads Session has expired, with subcode 463, and the person has to sign in again.
What happens after a password change or a security check?
Meta invalidates the person's tokens. A logout or a password change returns error 190 with subcode 460, The session is invalid because the user logged out, and Meta warns that security events can invalidate tokens before their expected expiration. Subcodes 459 and 464 mean the account itself needs attention: the person has to log in at facebook.com to correct an issue, then sign in to the app again. Otherwise the fix is a fresh sign-in, by that person or by someone else with a role on the Page.
What happens when the person loses their role on the Page?
Their Page token stops working with error 190, subcode 492, which Meta describes as the user associated with the Page access token no longer having an appropriate role on the Page. Tokens are issued per Page, person and app, so the tokens of other people with a role keep working. The fix is to connect the Page again from an account that still has full control or task access, ideally one that is not about to leave the business.
What happens when someone removes the app in Business integrations?
Meta invalidates the user access tokens the app held for that person, and the Page tokens read with them stop working as well, with error 190, subcode 458: the user has not authorized the application. People remove an app in Facebook's settings, under Business integrations, and Meta then calls the app's deauthorize callback. A system-user token is ended the same way from Business Manager, under Business Settings, Integrations, Connected apps, and an app can end its own access with DELETE /{user-id}/permissions.
Do Page permissions expire after 90 days?
Two different 90-day rules exist, and only one reaches Page permissions. Data access expiration, which cuts an app off 90 days after the person was last active, does not apply to pages_show_list, pages_manage_posts, pages_messaging, read_insights and the other Page permissions Meta lists as not expiring. Permission expiration does: a permission the app has not used for 90 days can expire, even one approved in App Review, and the person must grant it again. Calls that need it fail with code 10 or one in the 200 range until a new sign-in grants it.
Can the whole app lose access?
Yes, in three documented ways, which Meta warns of with an urgent notification in the App Dashboard's alerts inbox. An app with no logins, no Graph API or Marketing API calls and no webhook notifications for 90 days is deemed inactive, and Meta invalidates all its tokens; restoring it from the App Dashboard upgrades it to the latest version, but old tokens stay invalid and permissions dropped for disuse go back through App Review. The annual Data Use Checkup has to be completed, and breaking Meta's terms or policies can limit API access or revoke permissions.
What happens when Meta restricts the Page?
The restricted actions fail: error 368, temporarily blocked for policy violations, or for messages code 10 with subcode 1893063. Meta's Page Integrity API says which: GET /{page-id}/page_status, with pages_manage_metadata, returns a status of ok, warning, restricted or suspended, each active restriction, such as page_publish, page_read_only, page_messaging or page_messaging_api, with its expiration_time, and recommended actions such as FILE_APPEAL. The business_integrity webhook field reports changes as they happen.
Why do events stop while API calls still work?
Because webhooks fail on their own terms. After an hour of failed deliveries, Meta sends a Webhooks Disabled alert and unsubscribes the app from the Page until it subscribes again, and Meta sends nothing at all for a Page that has turned off the App platform in its App Settings. The token can stay valid through both, so after an outage check GET /{page-id}/subscribed_apps and, once the endpoint answers again, POST to it with the Page's token.
How do you catch a broken connection before a post fails?
By checking on a schedule, since Meta does not notify an app when a token becomes invalid. A light call such as GET /{page-id}?fields=id,name with the Page token fails the same way a post would. debug_token, called with the app's ID and secret as the access token, returns is_valid, expires_at and the granted scopes, plus the error code and subcode for a token that no longer works; page_status reports restrictions, and the deauthorize callback announces a removed app.
curl -G "https://graph.facebook.com/v26.0/debug_token" \
--data-urlencode "input_token=$PAGE_TOKEN" \
--data-urlencode "access_token=$APP_ID|$APP_SECRET"
# data.is_valid, data.expires_at, data.scopes, data.granular_scopes,
# and data.error.code with data.error.subcode once the token stops workingHow do you reconnect a Page?
With the same flow that connected it, run by someone who still has a role on the Page, after fixing the cause where there is one: a checkpointed account logs in at facebook.com, a restriction goes through its recommended action, and a failing endpoint answers 200 again. The new sign-in returns new token strings, so replace the stored ones rather than keeping both:
What does easyCoexistence do when a Page connection breaks?
It watches for the breaks it can see and tells you about them. Every 6 hours it checks each connected Page with GET /{page-id}?fields=id,name, and when Meta refuses the token with error 190 or 102, at that check or in any tool call, the Page is marked Reconnect needed, its owner gets one email and a partner platform receives channel.disconnected. Other refusals, such as a missing permission or a policy block, come back in the tool's result with Meta's code and message.
When someone removes the app under Business integrations, Meta's deauthorize callback reaches easyCoexistence, which removes the Pages that person connected, deletes their tokens and event destinations, takes them off the bill and sends channel.removed. Signing in again from the dashboard brings a Page back as the same connection, with its comment rules and automations, subscribed again to feed, messages and mention. After a Reconnect needed status the event destination stays as well; after a removal, set_social_webhook_destination sets it again with a new secret.
Common mistakes
- Retrying error 190. A refused token fails the same way on each call, and only a new sign-in by someone with a role on the Page produces a valid one.
- Reconnecting to lift a restriction. A new token leaves the Page's status as it was; the recommended actions in page_status, such as an appeal, are what change it.
- Requesting a permission the product rarely uses. Left unused for 90 days it can expire, and the calls that need it then fail; ask for it when the feature ships.
- Keeping the old token after a reconnect. The new sign-in returns a different token string, and a job still holding the old one keeps failing with 190.
US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Does a Page token stop working when the 60-day user token expires?
Not if it was read from /me/accounts with that long-lived user token: such a Page token has no expiration date, though the causes on this page can still end it.
Will Meta tell me when a Page token stops working?
Not for a token that goes invalid: the next call returns the error. Meta does call the app's deauthorize callback when someone removes the app, and it warns of app-wide risks in the App Dashboard's alerts inbox.
Can another person's token keep the Page connected?
Yes. Page tokens are issued per Page, person and app, so a token from someone else who still has a role on the Page keeps working when one person's access ends.
How much does easyCoexistence cost for a Facebook Page?
US$ 9 to US$ 0.75 per connection per month, set by how many connections you have, with each Page counted as one and the first 3 days free.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on