Troubleshoot Claude Tag in channels and DMs changedclaude-tag/users/troubleshooting
Nearest release: v2.1.239, published 9 hours before 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+73added
Lines−53removed
From line
106
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits31to this page, all time
### I hit repeated API server errors ### I hit API rate limits ### I got disconnected partway through ### A session link Claude posted shows a not-found page ### I hit repeated API server errors and stopped after retrying ### I hit API rate limits and stopped after retrying ### I lost the connection to this session's container mid-turn
The whole hunk
from line 106, old and new numbered
/
from line 106
106106
107107**What you see**
108108
109Mentions in a channel shared with another company get no reaction and no reply, ever.
109Mentions in a channel shared with another company get no answer. A direct mention gets a short notice that Claude doesn't respond there; anything else gets nothing.
110110
111111**What it means**
112112
113Claude doesn't operate in Slack Connect channels, the ones shared with another company. This holds regardless of admin settings; mentions there are dropped without a reply. See [externally shared channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
113Claude doesn't operate in Slack Connect channels, the ones shared with another company. This holds regardless of admin settings. A direct mention gets the reply "This channel is shared with another organization through Slack Connect, and Claude doesn't respond in Slack Connect channels yet." Other messages there are dropped without a reply. See [externally shared channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
114114
115115A channel shared across workspaces inside your Enterprise Grid isn't silent; what happens there depends on how those workspaces connect to Claude. When every workspace in the channel belongs to your one Claude organization, Claude answers, but with only your organization's default access and settings, so a repository or an instruction set up for that channel doesn't apply. A notice in the thread points this out from time to time. When the workspaces are connected to different Claude organizations, you see "This channel is shared among several Claude workspaces, so Claude cannot respond here" instead of an answer.
116116
from line 144
144144
145145Claude replies in the channel:
146146
147> Claude doesn't respond in channels that include guests. You can remove the guests from this channel (Channel details -> Members -> filter by "guests"), or a claude.ai organization owner can allow it here.
147> Claude doesn't respond in channels that include guests. You can remove the guests from this channel (Channel details -> Members -> filter by "guests"), or a claude.ai organization owner can allow it in Claude Tag settings under Advanced -> "Allow Claude to work in channels with guests".
148148
149149**What it means**
150150
from line 230
230230
231231The messages in this section mean a session started and then stopped partway through. In most cases the work isn't lost, and the same thread picks up where it stopped. Each entry says whether anything needs redoing.
232232
233### I hit repeated API server errors and stopped after retrying
233### I hit repeated API server errors
234234
235235**What you see**
236236
237237Claude posts in the thread:
238238
239> I hit repeated API server errors and stopped after retrying. Mention me to continue.
239> I hit repeated API server errors. I'll retry automatically in about 2 minutes — no need to do anything. Mention me to retry sooner.
240240
241The related messages "I hit repeated 529 Overloaded errors (the API is at capacity) and stopped after retrying. Mention me to continue." and "The API request timed out and I stopped after retrying. Mention me to continue." behave the same way.
241The related messages that start "Claude is over capacity right now" and "I hit API rate limits" behave the same way. The wait Claude names grows with each retry.
242242
243If the retries run out, or the session isn't a thread session, the message ends "and stopped after retrying. Mention me to continue." instead. "The API request timed out and I stopped after retrying. Mention me to continue." and "An API server error cut my last response short, so it may be incomplete. Mention me to continue." always take that form.
244
243245**What it means**
244246
245The API serving the session returned repeated errors, so Claude stopped rather than keep retrying. The work isn't lost.
247The API serving the session returned repeated errors. The work isn't lost. When the message says Claude will retry automatically, the same conversation wakes again on its own, up to three times; a newer message from you in the thread cancels the pending retry.
246248
247249**How to resolve**
248250
249Mention Claude in the same thread; it picks up where it stopped.
251Nothing, when the message says Claude will retry automatically; wait for it. Mention Claude in the same thread to retry sooner, or when the message asks you to.
250252
251### I hit API rate limits and stopped after retrying
253### I hit API rate limits
252254
253255**What you see**
254256
255257Claude posts in the thread:
256258
257> I hit API rate limits and stopped after retrying. Wait a moment, then mention me to continue.
259> I hit API rate limits. I'll retry automatically in about 2 minutes — no need to do anything. Mention me to retry sooner.
258260
261When the retries run out, the message is "I hit API rate limits and stopped after retrying. Wait a moment, then mention me to continue."
262
259263**What it means**
260264
261265The Claude API rate-limited your organization's traffic partway through the turn. The work isn't lost. Rate limits are about momentary request rate, not accumulated usage: a single task makes many API requests in short bursts, so this can appear on an organization's very first request. It isn't the channel spend limit, and it doesn't mean anything is misconfigured.
from line 266
262266
263267**How to resolve**
264268
265Wait a moment, then mention Claude in the same thread; it picks up where it stopped. If it recurs constantly across channels, the organization's sustained traffic is above its rate limits; an admin can stagger heavy use or contact their account team about limits.
269Wait for the automatic retry, or wait a moment and mention Claude in the same thread; it picks up where it stopped. If it recurs constantly across channels, the organization's sustained traffic is above its rate limits; an admin can stagger heavy use or contact their account team about limits.
266270
267271If your message mentions a spend limit instead, that's a different problem; see [You've reached a Claude Tag spend limit](#you%E2%80%99ve-reached-a-claude-tag-spend-limit).
268272
from line 292
288292
289293Claude posts in the thread:
290294
291> Claude couldn't clone a repository for this session. Mention Claude in this thread to retry.
295> Claude couldn't clone a repository for this session. This can be temporary (for example a GitHub rate limit) — mention Claude in this thread to retry in a few minutes. If it keeps happening, this session may lack access to a repository it needs, or its credentials or integration may need to be reconnected.
292296
293297**What it means**
294298
295The clone failed when the session started. A one-off failure is transient; the same repository failing every time usually means it isn't granted for this channel.
299The clone failed when the session started. A one-off failure is transient; the same repository failing every time usually means it isn't granted for this channel, or the connection it depends on needs to be reconnected.
296300
297301**How to resolve**
298302
299Mention Claude in the same thread to retry. If the same repository fails every time, send your admin [the GitHub access entry](/docs/claude-tag/admins/troubleshooting#github-doesn%E2%80%99t-work-in-this-channel).
303Wait a few minutes, then mention Claude in the same thread to retry. If the same repository fails every time, send your admin [the GitHub access entry](/docs/claude-tag/admins/troubleshooting#github-doesn%E2%80%99t-work-in-this-channel).
300304
301### I lost the connection to this session's container mid-turn
305### I got disconnected partway through
302306
303307**What you see**
304308
305309Claude posts in the thread:
306310
307> I lost the connection to this session's container mid-turn — the work I was doing may not have finished. Mention me to resume.
311> I got disconnected partway through and may not have finished. Reconnecting and resuming automatically — usually within a few minutes, though a slow recovery can take much longer. Mention me if I don't follow up.
308312
313When Claude reconnects, it edits that message to "I reconnected and I'm carrying on where I left off. No need to mention me." When automatic recovery isn't armed, the message is "I got disconnected partway through and may not have finished. Mention me to pick up where I left off." instead.
314
309315You can see it in a thread where you're working with Claude, including a direct-message thread; Claude doesn't post it in a channel it's only watching or from a routine.
310316
311317**What it means**
from line 320
314320
315321**How to resolve**
316322
317Mention Claude in the same thread. Claude resumes there and continues from the conversation; ask it to check on the step it was working on and redo anything that didn't finish. If the same notice comes back, the underlying problem hasn't cleared yet. Wait a few minutes and mention Claude again.
323Wait for the reconnect message, or mention Claude in the same thread when the message asks you to. Claude resumes there and continues from the conversation; ask it to check on the step it was working on and redo anything that didn't finish. If the same notice comes back, the underlying problem hasn't cleared yet. Wait a few minutes and mention Claude again.
318324
319325### Something went wrong and I couldn't finish this turn
320326
from line 402
396402
397403Verify what stuck by asking what it remembers about the channel. See [What Claude Tag remembers](/docs/claude-tag/users/memory).
398404
405### A session link Claude posted shows a not-found page
406
407**What you see**
408
409You open a link to a session on claude.ai that Claude posted in Slack, such as the "open the session" link in a routine's completion message, and claude.ai shows a not-found page instead of the session.
410
411**What it means**
412
413A session Claude ran from a channel belongs to Claude's own identity rather than to the person who asked, so claude.ai shows it only to accounts in the Claude organization paired with the workspace, and then only to people who could see the conversation in Slack. Any workspace member can open a session from a public channel; a session from a private channel opens only for members of that channel and the person who started it. Anyone else sees not-found rather than a permission error.
414
415**How to resolve**
416
417Sign in to claude.ai with the account that belongs to the organization paired with your workspace. claude.ai matches you to your Slack identity through a connected Slack account or, failing that, through the email address on your Claude account, so if your Claude email differs from your Slack email, connect your Slack account first; DM `@Claude` and it prompts you. If the session came from a private channel, ask to be added to the channel.
418
399419## Access and connections
400420
401421### A connection my admin added isn't showing up
from line 523
503523
504524Claude posts in the thread:
505525
506> You've reached a Claude Tag spend limit. Org admins can raise it in claude.ai admin settings. Once the limit is raised, mention me to retry.
526> You've reached a Claude Tag spend limit. A Claude.ai organization owner can raise it in Claude.ai admin settings. Once the limit is raised, mention me to retry.
507527
508528You may also see a heads-up before you hit the limit. It starts "Heads up — your organization has used *N%* of its monthly Claude Tag spend limit." for the organization limit, or "Heads up — this channel has used *N%* of its monthly Claude Tag spend limit." for a channel limit.
509529
510530**What it means**
511531
512Usage hit a cap an admin set, either for the whole organization or for this channel. A rate limit looks similar but is a different problem, and raising the spend limit doesn't clear it. If your message says "Hit the session rate limit — try again in a few seconds." (or "in \~Ns" when Claude knows the wait), too many sessions started at once. Wait a moment, then mention Claude again.
532Usage hit a cap an admin set, either for the whole organization or for this channel. A rate limit looks similar but is a different problem, and raising the spend limit doesn't clear it. If your message says "Hit the session rate limit — try again in a few seconds." (or "in about Ns" when Claude knows the wait), too many sessions started at once. Wait a moment, then mention Claude again.
513533
514534**How to resolve**
515535
from line 564
544564
545565Claude replies in the DM:
546566
547> Your Claude account is connected, but it doesn't have access in this organization — usually this means your admin hasn't assigned you a seat that includes Claude Code. Ask them to add one, then mention me to retry.
567> Your Claude account is connected, but it doesn't have access in this organization yet, usually because it needs a seat that includes Claude Code. A Claude admin can add one in your organization's settings. Once they do, mention me here and I'll pick this back up.
548568
549569The Claude app's **Messages** tab and Slack's assistant panel both count as DMs even though neither looks like one, so this message can appear when you thought you were using a channel.
550570
No line in this hunk matches that.