Troubleshoot federated cloud access changedclaude-tag/admins/federated-access/troubleshooting
Nearest release: v2.1.280, published 16 hours after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+6added
Lines−6removed
From line
75
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits13to this page, all time
The whole hunk
from line 75, old and new numbered
/
from line 75
7575
7676## Errors Claude reports in the thread
7777
78When a request from a channel can't be sent with a federated credential, it fails with an HTTP status and a one-line reason, which Claude usually quotes. Reasons with HTTP 403 and 502 end with the connection's name in parentheses, for example `("gateway.example.com")`. The two 503 reasons don't name the connection.
78When a request can't be sent with a federated credential, it fails with an HTTP status and a one-line reason, which Claude usually quotes. Reasons with HTTP 403 and 502 end with the connection's name in parentheses, for example `("gateway.example.com")`. The two 503 reasons don't name the connection.
7979
8080Messages that begin "request blocked" come with HTTP 403. The request was refused on purpose, and retrying won't help. A 503 is temporary. A 502 usually means AWS, Google Cloud, or your authorization server refused the token exchange. A response from your gateway or from the cloud API itself reaches Claude as is, so those show as whatever status the other side returned.
8181
from line 87
8787
8888**What it means**
8989
90Federated connections work only in Slack channels, where Claude acts under your organization's [agent identity](/docs/claude-tag/concepts/agent-identity). The request came from a direct message, or from another session running under a person's own account, which has no agent identity for the token to name.
90Federated connections work only in agent sessions, such as a Slack channel, where Claude acts under your organization's [agent identity](/docs/claude-tag/concepts/agent-identity). The request came from a personal session, such as a [direct message](/docs/claude-tag/concepts/agent-identity#direct-message-channels) with `@Claude`. A personal session runs under a person's own account and has no agent identity for the token to name.
9191
9292**How to resolve**
9393
94Use the connection from a channel whose scope has the bundle attached. No setting enables it in direct messages.
94Use the connection from a channel whose scope has the bundle attached. No setting enables federated connections in personal sessions.
9595
9696### request blocked: this credential's audience isn't registered as a gateway for this organization
9797
No line in this hunk matches that.