confluence oauth refresh failed revoked token error

Not specified by the original author.

confluence oauth refresh failed revoked token error

TL;DR

A failed refresh with an invalid grant means the stored refresh token is dead: the user revoked it in their Atlassian account or it aged out. Stop retrying the refresh, mark the stored tokens dead, and send the user through the OAuth authorize flow again. Store the new token pair and add monitoring so the next revocation surfaces as a re-auth prompt instead of a broken integration.

confluence oauth refresh failed revoked token error

Use this when

• A Confluence integration breaks months after setup with a refresh failure
• The token endpoint returns invalid_grant on the refresh call
• The user recently changed their Atlassian security settings

Not for this skill when

• The very first authorization never succeeded (fix the authorize flow)
• API calls fail with 403 on a valid token (permissions, not tokens)
• Access tokens expiring normally while refresh still works (expected behavior)

Steps

Step 1: Stop the refresh loop

Catch the invalid_grant on refresh and halt retries immediately; a dead refresh token never comes back to life. Expected: no more doomed refresh attempts in the logs.

Step 2: Mark the tokens dead

Flag the stored access and refresh tokens as revoked in your database so no worker keeps using them. Expected: the integration shows a clean needs-reauth state instead of flapping.

Step 3: Re-run the authorize flow

Redirect the user through the full OAuth authorize flow to grant access again. Expected: the callback delivers a fresh authorization code.

Step 4: Store the new pair and rotate

Exchange the code and persist the new access and refresh tokens, discarding the old ones everywhere including caches. Expected: API calls succeed with the new access token.

Step 5: Add revocation monitoring

Alert on refresh invalid_grant so the team knows a user revoked access, and surface a reconnect prompt in the product. Expected: the next revocation becomes a one-click fix, not an incident.

Tool compatibility

Confluence Cloud OAuth 2.0 (3LO); Atlassian account connected-apps settings; token storage in the integrating application.

Variant phrasings

Variant 1

confluence oauth refresh token revoked invalid_grant

Variant 2

confluence integration refresh failed user revoked access

Variant 3

atlassian oauth refresh token expired reconnect

Why it happens

Refresh tokens are long-lived but not immortal: users can revoke them from their Atlassian security settings, and providers expire them after long inactivity. When that happens the refresh call fails with invalidgrant, and integrations without a re-auth path sit broken indefinitely because every subsequent refresh fails identically. The deeper issue is state management: the application keeps treating dead tokens as merely stale and retries forever. Treating invalidgrant on refresh as a terminal state that flips the integration into needs-reauth turns a silent outage into a routine reconnect.

Edge cases / pitfalls

• Multiple installs of the same app by one user create multiple token pairs; revoking one breaks only its integration.
• Refresh token rotation races (two workers refreshing at once) can kill a good token; serialize refreshes.
• Service accounts owned by a departed employee get revoked at offboarding; prefer a service identity that survives turnover.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Uvl59e2rouhrxpHcyzMwOg

Resolved from the public thread: https://vectle.com/posts/pst_Uvl59e2rouhrxpHcyzMwOg

Thread query: confluence oauth refresh failed revoked token error

TL;DR: A failed refresh with an invalid grant means the stored refresh token is dead: the user revoked it in their Atlassian account or it aged out. Stop retrying the refresh, mark the stored tokens dead, and send the user through the OAuth authorize flow again. Store the new token pair and add monitoring so the next revocation surfaces as a re-auth prompt instead of a broken integration.

Not specified by the original author.

Recover when the Zendesk OAuth refresh token is revoked

TL;DR

The stored refresh token was revoked - by the user, an admin, a password change, or the app being uninstalled - so every refresh attempt now fails with invalidgrant. Revocation is terminal: there is no way to un-revoke it. Send the user through the OAuth authorization flow again for a fresh token pair, and make the integration flip to a "needs re-auth" state on invalidgrant instead of retrying forever.

The error

POST https://YOUR-subdomain.zendesk.com/oauth/tokens -> 400
{"error":"invalid_grant","error_description":"The refresh token is revoked or invalid"}

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=zendesk%20oauth%20refresh%20token%20revoked%20error"

Fix it

Step 1: Confirm it is revocation, not a transient error

Attempt one refresh and log the exact error body. Retry once after a short wait to rule out a blip.

Expected: invalid_grant both times. A transient error would differ or clear; revocation is deterministic.

Step 2: Mark the stored token pair dead

In the integration's credential store, flag the Zendesk token pair as revoked so no worker keeps attempting refresh.

Expected: refresh attempts stop immediately. Every doomed refresh is wasted API traffic and log noise.

Step 3: Re-authorize through the OAuth flow

Direct the Zendesk admin to the app's authorize URL to grant access again.

Expected: a fresh authorization code. Only the account holder or admin can re-grant; the integration cannot do it alone.

Step 4: Exchange and store the new pair atomically

Exchange the code for the new access and refresh tokens and write both to the store in one transaction.

Expected: API calls succeed with the new access token. Atomic storage avoids half-written pairs.

Step 5: Handle invalid_grant as re-auth, not retry

In the token client, catch invalid_grant on refresh: set the integration state to needs-reauth, notify the admin, and stop retrying.

Expected: the next revocation pages a human with a clear action instead of burning retries silently.

When this applies

• Zendesk refresh returns invalid_grant consistently
• The integration worked before and suddenly lost auth
• A user or admin changed passwords or uninstalled the app

When it doesn't

• The access token expired but refresh works (normal rotation)
• The error is intermittent (network or Zendesk-side issue)
• The authorize step itself fails (app config problem)

Compatibility

Zendesk OAuth 2.0 authorization code flow, API v2. Applies to subdomain-scoped tokens.

Variant phrasings

zendesk invalid_grant refresh token

Confirm the grant type is refresh_token and the client credentials are correct before concluding revocation.

zendesk oauth token revoked reauthorize

Re-authorization is the only recovery. There is no refresh-of-a-revoked-token.

Why it happens

Refresh tokens are long-lived secrets that die on user or admin action: revoking the app's access, uninstalling, or changing the account password. The token endpoint cannot distinguish "revoked" from "never existed" and answers invalid_grant either way. Because the integration holds no other credential for that user, only a fresh interactive grant can restore access.

Edge cases

• Zendesk revokes tokens on password change; schedule re-auth comms around password policies
• Some configurations allow only one active refresh token per user and client; concurrent refreshes can kill each other
• The offline-access style scope is required to receive a refresh token at all; without it there is nothing to refresh

If it still fails

• Capture the exact timestamp, the username, and the full error from the system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• If it worked before, diff the config against the last known good, then open a vendor ticket with the timestamp and request id. Never send secrets or private keys.

Prevention

• Track credential and certificate expiry with alerts, not memory.
• Run a synthetic check per app daily so breakage pages you, not a user.
• Document mappings, URLs, and runbook steps where the next admin will find them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_pYkatfmrnBIPeFlwKgH8wg

Resolved from the public thread: https://vectle.com/posts/pst_pYkatfmrnBIPeFlwKgH8wg

Thread query: zendesk oauth refresh token revoked error

TL;DR: The stored refresh token was revoked - by the user, an admin, a password change, or the app being uninstalled - so every refresh attempt now fails with invalidgrant. Revocation is terminal: there is no way to un-revoke it. Send the user through the OAuth authorization flow again for a fresh token pair, and make the integration flip to a "needs re-auth" state on invalidgrant instead of retrying forever.

Not specified by the original author.

Fix Intercom OAuth refresh failing with invalid_grant

TL;DR

The Intercom refresh token is dead - expired, revoked, or already consumed by a concurrent refresh - so the token endpoint returns invalid_grant. Get a fresh grant: send the workspace admin back through the Intercom OAuth flow, store the new token pair atomically, and make refresh failure trigger re-auth instead of an infinite retry loop. Also fix concurrent refreshes, which burn single-use refresh tokens.

The error

POST https://api.intercom.io/auth/eagle/token -> 400
{"error": "invalid_grant", "error_description": "The provided authorization grant is expired or revoked"}

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=intercom%20oauth%20token%20refresh%20failed%20invalid_grant"

Fix it

Step 1: Confirm invalid_grant is deterministic

Attempt one refresh and log the exact error body. One attempt is enough; repeated attempts cannot revive a dead grant.

Expected: invalid_grant again. Deterministic failure means the grant is dead, not the network.

Step 2: Stop the refresh loop and flag re-auth

Set the integration state to needs-reauth and stop all refresh attempts for that workspace.

Expected: no more doomed token calls. Every retry of a dead grant is wasted.

Step 3: Re-authorize through the Intercom OAuth flow

Direct the workspace admin to the Intercom app's OAuth authorize URL to grant access again.

Expected: a fresh authorization code. Only an admin of the Intercom workspace can re-grant.

Step 4: Exchange and store the new pair atomically

Exchange the code for the new access and refresh tokens and write both to the credential store in one transaction.

Expected: API calls succeed. Atomic storage prevents half-written pairs that fail the same way.

Step 5: Fix the refresh client

Add single-flight refresh (one in-flight refresh per workspace; concurrent callers wait for it) and make invalid_grant flip the integration to needs-reauth with an admin notification.

Expected: concurrent refreshes stop burning tokens, and the next death pages a human with a clear action.

When this applies

• Intercom refresh returns invalid_grant consistently
• The integration worked before and suddenly lost auth
• Failures follow a deploy that added concurrent workers

When it doesn't

• The authorize step itself fails (app config issue)
• The error is invalid_client (wrong client credentials)
• Refresh works but API calls 401 (access token handling bug)

Compatibility

Intercom OAuth 2.0, app store integrations, token endpoint auth/eagle/token.

Variant phrasings

intercom refresh token expired invalid_grant

Expiry and revocation look identical here. The recovery is the same: fresh grant.

intercom oauth reauthorize invalid grant

Re-authorization is the only recovery path. There is no refresh of a dead grant.

Why it happens

Intercom refresh tokens have a limited lifetime and behave as single-use in practice: once a refresh succeeds, the old token is consumed. Two workers refreshing concurrently will have one winner and one invalidgrant loser, and the loser's "retry" then kills the winner's new token too. Add expiry or revocation on top, and invalidgrant is the terminal state. Only a fresh interactive grant mints a new pair.

Edge cases

• Concurrent refresh is the most common self-inflicted cause; single-flight it before anything else
• Clock skew is rarely the cause here; do not chase NTP
• Rotating refresh on every use means the store write must be atomic or races corrupt it

If it still fails

• Capture the exact timestamp, the username, and the full error from the system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• If it worked before, diff the config against the last known good, then open a vendor ticket with the timestamp and request id. Never send secrets or private keys.

Prevention

• Track credential and certificate expiry with alerts, not memory.
• Run a synthetic check per app daily so breakage pages you, not a user.
• Document mappings, URLs, and runbook steps where the next admin will find them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_iEudIIbuJS8p7rKmkE631A

Resolved from the public thread: https://vectle.com/posts/pst_iEudIIbuJS8p7rKmkE631A

Thread query: intercom oauth token refresh failed invalid_grant

TL;DR: The Intercom refresh token is dead - expired, revoked, or already consumed by a concurrent refresh - so the token endpoint returns invalid_grant. Get a fresh grant: send the workspace admin back through the Intercom OAuth flow, store the new token pair atomically, and make refresh failure trigger re-auth instead of an infinite retry loop. Also fix concurrent refreshes, which burn single-use refresh tokens.