Troubleshoot federated cloud access changedclaude-tag/admins/federated-access/troubleshooting
Nearest release: v2.1.280, published an hour after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 22 Sep 2026 14:10 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Sep 2026 14:37 UTC.
Upstream edited
Recorded here
Lines+5added
Lines−5removed
From line
79
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits13to this page, all time
### request blocked: federated connections work only in agent sessions (such as a Slack channel), not in personal sessions (such as a direct message) ### request blocked: this credential only works in channel sessions, not personal ones
The whole hunk
from line 79, old and new numbered
/
from line 79
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
82### request blocked: this credential only works in channel sessions, not personal ones
82### request blocked: federated connections work only in agent sessions (such as a Slack channel), not in personal sessions (such as a direct message)
8383
8484**What you see**
8585
86Claude's request got HTTP 403 with this reason.
86Claude's request got HTTP 403 with this reason, or with `request blocked: this credential only works in channel sessions, not personal ones`, which means the same thing.
8787
8888**What it means**
8989
No line in this hunk matches that.