OAUTH_TOKEN_NOT_FOUND

What this means

Glean doesn't have stored credentials for this teammate and tool. This typically happens when:

• The teammate hasn't connected their account to the tools yet.
• Credentials were cleared.
• An admin reset the teammate's tools authorization.
• A previously stored token was removed because a background refresh failed.

What to do as a teammate

1. Run an agent that uses the tool, or trigger the tool directly.
2. When prompted, click Connect to authorize Glean to access the source system on your behalf.
3. Complete the OAuth flow in the source system and return to Glean.

What to do as an admin

If teammates can't connect or keep seeing this error:

1. Confirm the tools are set up in Admin console → Platform → Tools and that the authentication method, Central or Custom, is correctly configured.
2. If the tools uses the Central app, verify that any required site-level or org-level approvals are in place. For example, Jira tools require a Jira site admin to authorize the OAuth app for the Atlassian site before other teammates can connect.
3. If the tools uses a Custom OAuth app, verify the client ID, client secret, and callback URL are correct and that the app is still active in the source system.

If the teammate previously had a working connection that disappeared, a background token refresh likely failed and the stored token was removed. See OAUTH_TOKEN_REFRESH_FAILED for common causes and a re-authorization runbook.

For more guidance, see Troubleshooting tools authentication.

For additional assistance, contact Glean Support.