OAUTH_TOKEN_NOT_FOUND

What this means

Glean doesn't have stored credentials for this teammate and action. This typically happens when a teammate hasn't yet authorized the action, when credentials were cleared, or when an admin reset the teammate's action pack authorization.

What to do as a teammate

1. Run an agent that uses the action, or trigger the action 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 action pack is set up in Admin Console → Platform → Actions and that the authentication method (Central or Custom) is correctly configured.
2. If the action pack uses the Central app, verify that any required site-level or org-level approvals are in place. For example, Jira actions require a Jira site admin to authorize the OAuth app for the Atlassian site before other teammates can connect.
3. If the action pack 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.

For more guidance, see Troubleshooting actions authentication.

For additional assistance, contact Glean Support at https://support.glean.com.