Instagram error 190: Session has expired

Code 190 with subcode 463 is plain token expiry. Meta's error-handling reference describes 463 as "Login status or access token has expired, been revoked, or is otherwise invalid", and the message helpfully names the exact expiry timestamp. This is the classic signature of an Instagram integration that ran perfectly for a fixed period - an hour, or about 60 days - and then died at a predictable moment without any code change.

The period tells you which token you shipped. A short-lived user token lasts about an hour; a long-lived user token about 60 days. On the Messenger Platform route the production credential should be a Page access token derived from a long-lived user token - Meta documents that Page tokens obtained this way have no expiration date, though they still die if the issuing user loses access to the Page, deauthorizes the app, or changes their password (that variant is subcode 460). On the Instagram API with Instagram Login route, long-lived tokens must be refreshed before expiry with the refresh endpoint; a missed refresh lands here.

Everything else about your integration is untouched. Webhooks may even keep arriving while every reply fails with 463, because inbound delivery does not use your token. That asymmetry - inbound fine, outbound dead - is a strong 190 signal.

{
  "error": {
    "message": "Error validating access token: Session has expired on Tuesday, 19-Aug-26 04:00:00 PDT. The current time is Wednesday, 20-Aug-26 09:12:44 PDT.",
    "type": "OAuthException",
    "code": 190,
    "error_subcode": 463,
    "fbtrace_id": "Dq1rS8uV3wXy"
  }
}

Make token age observable: store issued-at and expected-expiry alongside the token, alert when a token crosses 80 percent of its lifetime, and run the refresh in a job with failure alerting rather than a fire-and-forget cron. Add a daily health check that calls the debug endpoint so an invalid credential is a monitoring event, not a customer report. Section 6 of the troubleshooting guide covers the full token lifecycle across both routes, and the 190 hub entry maps the other subcodes.