Troubleshoot Claude Tag in channels and DMs

claude-tag/users/troubleshooting Changed · +6 / -13 lines

 
 **What you see**
 
-Mentions in a Slack Connect channel, one shared with another company, get no answer, and usually no notice.
+Mentions in a channel shared with another company get no answer, and usually no notice.
 
 **What it means**
 
-By default, Claude is off in Slack Connect channels, and it posts no notice there. A Claude organization Owner turns it on with the [guest setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels), after which Claude replies with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works). If the setting is already **Allow** or **Channel only** and Claude still doesn't answer, one of two things is likely:
+Claude doesn't operate in Slack Connect channels, the ones shared with another company. This holds regardless of admin settings. Messages there get no reply. See [externally shared channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
 
-* The organization that runs Claude restricts it to its own members, and you're on the other side of the channel.
-* That organization installed Claude at the Enterprise Grid organization level, and the other company's workspace created the channel.
-
-See [Slack Connect channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
-
-If the mention gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," the thread started before the channel was shared. Mention `@Claude` in a new thread.
-
 A 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.
 
 Where guest access is restricted, you may first see "This channel is shared across multiple workspaces, and Claude can't verify whether it includes guests, so Claude can't respond here." If you ask Claude from another conversation to act in one of these channels, such as posting a message there, you see a reply that ends "Claude isn't available in channels shared across your Enterprise Grid".

 
 * Remove the guests from the channel. In Slack, open **Channel details** → **Members** and filter by "guests"; guests show a **guest** badge on their Slack profile.
 * Move the conversation to a channel with no guests.
-* Ask an admin of your Claude organization to change the guest setting for this channel, and send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels). They can let Claude reply with only the channel's own setup, or with full access. If you don't know who your organization's admins are, ask whoever set Claude up in your workspace.
+* Ask a claude.ai organization owner to allow Claude to respond in channels that include guests, and send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels). If you don't know who your organization's owners are, ask whoever set Claude up in your workspace.
 
 The guest access setting restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even when it's allowed to respond there. Removing the guests or moving the conversation to a channel with no guests restores search as well.
 

claude-tag/users/troubleshooting Changed · +12 / -5 lines

 
 **What you see**
 
-Mentions 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.
+Mentions in a Slack Connect channel, one shared with another company, get no answer, and usually no notice.
 
 **What it means**
 
-Claude 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).
+By default, Claude is off in Slack Connect channels, and it posts no notice there. A Claude organization Owner turns it on with the [guest setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels), after which Claude replies with [channel-only access](/docs/claude-tag/admins/restrict-access#how-channel-only-works). If the setting is already **Allow** or **Channel only** and Claude still doesn't answer, one of two things is likely:
+
+* The organization that runs Claude restricts it to its own members, and you're on the other side of the channel.
+* That organization installed Claude at the Enterprise Grid organization level, and the other company's workspace created the channel.
+
+See [Slack Connect channels](/docs/claude-tag/admins/restrict-access#externally-shared-channels).
+
+If the mention gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," the thread started before the channel was shared. Mention `@Claude` in a new thread.
 
 A 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.
 

claude-tag/users/troubleshooting Changed · +73 / -53 lines

### 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

 
 **What you see**
 
-Mentions in a channel shared with another company get no reaction and no reply, ever.
+Mentions 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.
 
 **What it means**
 
-Claude 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).
+Claude 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).
 
 A 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.
 

 
 Claude replies in the channel:
 
-> 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.
+> 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".
 
 **What it means**
 

 
 The 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.
 
-### I hit repeated API server errors and stopped after retrying
+### I hit repeated API server errors
 
 **What you see**
 
 Claude posts in the thread:
 
-> I hit repeated API server errors and stopped after retrying. Mention me to continue.
+> I hit repeated API server errors. I'll retry automatically in about 2 minutes — no need to do anything. Mention me to retry sooner.
 
-The 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.
+The 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.
 
+If 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.
+
 **What it means**
 
-The API serving the session returned repeated errors, so Claude stopped rather than keep retrying. The work isn't lost.
+The 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.
 
 **How to resolve**
 
-Mention Claude in the same thread; it picks up where it stopped.
+Nothing, 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.
 
-### I hit API rate limits and stopped after retrying
+### I hit API rate limits
 
 **What you see**
 
 Claude posts in the thread:
 
-> I hit API rate limits and stopped after retrying. Wait a moment, then mention me to continue.
+> I hit API rate limits. I'll retry automatically in about 2 minutes — no need to do anything. Mention me to retry sooner.
 
+When the retries run out, the message is "I hit API rate limits and stopped after retrying. Wait a moment, then mention me to continue."
+
 **What it means**
 
 The 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.

 
 **How to resolve**
 
-Wait 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.
+Wait 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.
 
 If 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).
 

 
 Claude posts in the thread:
 
-> Claude couldn't clone a repository for this session. Mention Claude in this thread to retry.
+> 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.
 
 **What it means**
 
-The 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.
+The 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.
 
 **How to resolve**
 
-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).
+Wait 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).
 
-### I lost the connection to this session's container mid-turn
+### I got disconnected partway through
 
 **What you see**
 
 Claude posts in the thread:
 
-> I lost the connection to this session's container mid-turn — the work I was doing may not have finished. Mention me to resume.
+> 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.
 
+When 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.
+
 You 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.
 
 **What it means**

 
 **How to resolve**
 
-Mention 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.
+Wait 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.
 
 ### Something went wrong and I couldn't finish this turn
 

 
 Verify what stuck by asking what it remembers about the channel. See [What Claude Tag remembers](/docs/claude-tag/users/memory).
 
+### A session link Claude posted shows a not-found page
+
+**What you see**
+
+You 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.
+
+**What it means**
+
+A 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.
+
+**How to resolve**
+
+Sign 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.
+
 ## Access and connections
 
 ### A connection my admin added isn't showing up

 
 Claude posts in the thread:
 
-> 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.
+> 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.
 
 You 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.
 
 **What it means**
 
-Usage 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.
+Usage 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.
 
 **How to resolve**
 

 
 Claude replies in the DM:
 
-> 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.
+> 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.
 
 The 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.
 

claude-tag/users/troubleshooting First recorded · 595 lines, first recorded

# Troubleshoot Claude Tag in channels and DMs ## No response or silence ### Mentioning @Claude does nothing at all ### Claude replies to me but not to a teammate ### Claude reacted or started thinking, then never replied ### Claude says my session is queued or failed to start ### Claude didn't react to a message I edited ### Claude never responds in a channel shared with another company ### Couldn't check this channel just now ### Claude doesn't respond in channels that include guests ## Too many or wrong responses ### Claude gave me a confident but wrong answer ### Claude replies to every message in a thread ### I want to take back something I sent ### This conversation is too long for me to process ## Claude stopped mid-task ### I hit repeated API server errors and stopped after retrying ### I hit API rate limits and stopped after retrying ### This request needs usage credits that aren't available ### Claude couldn't clone a repository for this session ### I lost the connection to this session's container mid-turn ### Something went wrong and I couldn't finish this turn ## Lost or stale work ### Claude lost work it created earlier ### My old thread stopped working, but new threads are fine ### Claude picked the wrong repository ### Claude forgot instructions I gave it before ## Access and connections ### A connection my admin added isn't showing up ### Claude says it can't access a channel it read before ### Claude says it can't reach a tool or service ### A connector works on claude.ai but not in Slack ### Claude says it has no internet access or can't open a link ### Claude can't connect over SSH ### You've reached a Claude Tag spend limit ## DMs aren't working ### I get an environment error in a DM ### Your Claude account is connected, but it doesn't have access in this organization ### Your Claude admin has disabled sending direct messages to Claude ### Group DMs aren't supported ## Related resources

The first capture of this source. The page was already there, and this is what it said.

# Troubleshoot Claude Tag in channels and DMs

> Fixes for common Claude Tag problems in Slack. See no reply after a reaction, queued or failed sessions, lost work, missing connections, blocked links and websites, and DM or account errors.

export const BetaNote = () => <Info>Claude Tag is in public beta. Features and behavior described here may change before general availability.</Info>;

<BetaNote />

When something goes wrong mid-conversation, the cause is usually one of a small set. Each entry below has the same three parts: what you see, what it means, and how to resolve it. For setup and credential errors, see the [admin troubleshooting page](/docs/claude-tag/admins/troubleshooting).

Many fixes end with something to send your admin. On this page that means whoever manages your organization's Claude account at claude.ai, and it's often not the same person as your Slack administrator. If you don't know who that is, ask whoever set Claude up in your workspace.

## No response or silence

### Mentioning @Claude does nothing at all

**What you see**

`@Claude` gets no reaction and no reply.

**What it means**

Total silence has several possible causes, from the app not being installed to the channel being turned off, and the checks below separate them.

**How to resolve**

Work through these in order. Each step says what success looks like and where to go if it fails.

1. **Is the Claude app installed in this workspace?** Start typing `@Claude` in any channel. **Works**: Slack autocompletes to a Claude app with an app badge; if more than one Claude app appears, check with your admin which one to use. **Fails**: nothing autocompletes, or only a person named Claude appears. The app isn't installed; this needs your admin (send them the [setup overview](/docs/claude-tag/admins/setup-overview)).
2. **Is Claude in this channel?** Type `/invite @Claude` in the channel's message box, not in a thread reply. Slack rejects `/invite` inside threads ("/invite is not supported in threads. Sorry!"). **Works**: Slack posts "Claude was added to #channel" (or "is already in this channel"). Mention it again. **Fails**: Slack says you can't add apps to this channel (a Slack Connect or guest-restricted channel); try an internal channel instead.
3. **Is Claude Tag turned on for this channel?** Mention it again now that it's invited. **Works**: it reacts and replies. **Fails**: it replies "Claude is disabled in this channel" (the channel is set to **Off**), or it replies but behaves like the earlier Claude in Slack, with no channel memory and pull requests opening under your name rather than Claude's (the channel is set to **Legacy**). Either way this needs your admin (send them [Migrate from the earlier Claude in Slack](/docs/claude-tag/admins/restrict-access#migrate-from-the-earlier-claude-in-slack)).

If `@Claude` still gets no reaction and no reply after all three, send your admin [the admin entries for a silent workspace](/docs/claude-tag/admins/troubleshooting#nothing-responds). If the silence covers every channel across an Enterprise Grid, the fix needs a Slack organization admin rather than your Claude admin, so send the link to them.

### Claude replies to me but not to a teammate

**What you see**

Claude answers your mentions in a channel, and a teammate's mentions in the same channel get silence or a refusal.

**What it means**

Mentioning Claude in a channel doesn't require the sender to have a Claude account or seat, so by default anyone in the workspace can use it. Your organization can restrict that with the [member access setting](/docs/claude-tag/admins/restrict-access#members), in which case members outside the restriction are declined.

**How to resolve**

Have the teammate mention `@Claude` themselves and report the exact text of any reply; the reply is the diagnosis.

* No reaction and no reply at all: unusual when it works for you in the same channel; send your admin the exact channel and person.
* A message about guests: see [the guest entry below](#claude-doesn%E2%80%99t-respond-in-channels-that-include-guests).
* A message about permissions or access: your organization restricts who can use Claude; send your admin [the member access setting](/docs/claude-tag/admins/restrict-access#members).

### Claude reacted or started thinking, then never replied

**What you see**

Claude added a reaction to your message, or an "is thinking…" line appeared under it, but no reply arrived.

**What it means**

A reaction or an "is thinking…" line without a reply usually means Claude is still working, not that your message was dropped.

**How to resolve**

1. @-mention Claude in the same thread to ask for a status check.
2. If it has replied before in the thread, open the session from the link in its last message to watch live progress. Long tasks often show steady movement there while the Slack thread looks idle.
3. If the silence has stretched well past what the task should need, send [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session) in the thread; it archives the session and starts a fresh one that still reads the thread. Starting a new thread and restating the request also works.

<Warning>Restarting abandons whatever the session was midway through, and there's no way to resume it. A silent session may still be working through a long task, so treat `!restart` as a last resort.</Warning>

### Claude says my session is queued or failed to start

**What you see**

Claude posts in the thread:

> Still waiting for available capacity — your request is queued and will start automatically. Replies in this thread are picked up automatically.

Or, if the session never started:

> Session failed to start: the session container never connected — please try again

**What it means**

The first message means compute capacity is temporarily busy; the session starts on its own once capacity frees up. The second means the session didn't start at all, which is transient.

**How to resolve**

* For the capacity message, wait a few minutes; no action is needed. To add context while waiting, @-mention Claude in the same thread rather than starting a new one. A new thread only queues a second session behind the first.
* For the failed-start message, mention Claude in the same thread to retry. If the retry worked, the session starts and Claude begins the task.

### Claude didn't react to a message I edited

**What you see**

You edited a sent message to add `@Claude`, and nothing happened.

**What it means**

Editing a sent message to add a mention doesn't trigger a response; Claude only picks up mentions from new messages.

**How to resolve**

Send a new message with the mention included.

### Claude never responds in a channel shared with another company

**What you see**

Mentions in a channel shared with another company get no reaction and no reply, ever.

**What it means**

Claude 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).

A 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.

Where guest access is restricted, you may first see "This channel is shared across multiple workspaces, and Claude can't verify whether it includes guests, so Claude can't respond here." If you ask Claude from another conversation to act in one of these channels, such as posting a message there, you see a reply that ends "Claude isn't available in channels shared across your Enterprise Grid".

Each of these messages means the channel spans more than one workspace. The [admin entries on these messages](/docs/claude-tag/admins/troubleshooting#this-channel-is-shared-across-multiple-workspaces) explain what causes each one and what an admin can change.

**How to resolve**

Move the conversation to an internal channel that belongs to a single workspace, or to a DM, and mention Claude there.

### Couldn't check this channel just now

**What you see**

Claude replies in the channel:

> Couldn't check this channel just now. Please try again in a moment.

**What it means**

When your organization restricts Claude in channels that include guests (the default), Claude checks each channel for guests before replying. That check briefly failed, so Claude declined this reply rather than guess.

**How to resolve**

Mention Claude again; the check usually passes on retry. If the same channel hits this repeatedly, send your admin [the admin entry on this message](/docs/claude-tag/admins/troubleshooting#couldn%E2%80%99t-check-this-channel-just-now).

### Claude doesn't respond in channels that include guests

**What you see**

Claude replies in the channel:

> 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.

**What it means**

The channel includes at least one Slack guest account, and your organization restricts Claude in channels that include guests (the default).

**How to resolve**

Any of these fixes works:

* Remove the guests from the channel. In Slack, open **Channel details** → **Members** and filter by "guests"; guests show a **guest** badge on their Slack profile.
* Move the conversation to a channel with no guests.
* Ask a claude.ai organization owner to allow Claude to respond in channels that include guests, and send them [the guest access setting](/docs/claude-tag/admins/restrict-access#restrict-guest-channels). If you don't know who your organization's owners are, ask whoever set Claude up in your workspace.

The guest access setting restores replies, not workspace search. Claude can't search the workspace from a channel that includes guests, even when it's allowed to respond there. Removing the guests or moving the conversation to a channel with no guests restores search as well.

If the fix worked, a mention in the channel gets a reply.

## Too many or wrong responses

### Claude gave me a confident but wrong answer

**What you see**

Claude answered with certainty, and the answer is wrong or incomplete.

**What it means**

Claude can be wrong, including when it sounds certain. The most common wrong answer in Slack is an incomplete one, where Claude queried one source or one date range and reported the result as if it were the whole picture.

**How to resolve**

Before you share or act on a result, check the source links it posted, and ask it to show its work ("which channels did you search?" or "show me the query you ran"). If the answer is wrong, say so in the same thread with the correct answer; correcting it there is also how you steer the next attempt.

For numbers and facts that matter, the [definition-of-done habit](/docs/claude-tag/users/good-habits#give-every-task-a-definition-of-done) helps. Make "include the source for every figure" or "show me the query" part of the ask.

### Claude replies to every message in a thread

**What you see**

Claude answers messages in the thread that weren't addressed to it.

**What it means**

Once Claude is mentioned in a thread, it follows the whole conversation there and may reply to messages that weren't addressed to it.

**How to resolve**

Reply in the thread with an instruction such as "only respond when I @-mention you"; Claude follows that instruction for the rest of the thread.

### I want to take back something I sent

**What you see**

You edited or deleted a message, and Claude still acts on the original.

**What it means**

Claude has already read the original. An edit reaches it as a new update in the thread, so it may or may not act on the change, and it never undoes work already in progress. A deleted reply doesn't reach Claude at all.

**How to resolve**

Say so in a new reply ("ignore that, do X instead"), or start a fresh thread for a clean session.

### This conversation is too long for me to process

**What you see**

Claude posts in the thread:

> This conversation is too long for me to process and I couldn't finish this turn — please start a new thread to continue.

In a DM it ends with "Click *New Chat* in the top right to start a fresh session" instead.

**What it means**

The thread has grown past what one session can hold, and it stays too long forever; retrying there can't work.

**How to resolve**

Start a new thread. You can paste a summary of where the previous one left off.

## Claude stopped mid-task

The 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.

### I hit repeated API server errors and stopped after retrying

**What you see**

Claude posts in the thread:

> I hit repeated API server errors and stopped after retrying. Mention me to continue.

The 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.

**What it means**

The API serving the session returned repeated errors, so Claude stopped rather than keep retrying. The work isn't lost.

**How to resolve**

Mention Claude in the same thread; it picks up where it stopped.

### I hit API rate limits and stopped after retrying

**What you see**

Claude posts in the thread:

> I hit API rate limits and stopped after retrying. Wait a moment, then mention me to continue.

**What it means**

The 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.

**How to resolve**

Wait 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.

If 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).

### This request needs usage credits that aren't available

**What you see**

Claude posts in the thread:

> This request needs usage credits that aren't available and I couldn't finish this turn. Enable or purchase usage credits in claude.ai, then mention me to retry.

**What it means**

Your organization's usage credit balance can't cover the request, so the turn stopped. The session is still there.

**How to resolve**

An admin enables or purchases usage credits in claude.ai for your organization. Once that's done, mention Claude in the same thread to retry (adding credits doesn't restart the work on its own). The retry continues with the thread's conversation and context. [What survives between replies](/docs/claude-tag/concepts/how-it-works#what-survives-between-replies) covers what else carries over.

### Claude couldn't clone a repository for this session

**What you see**

Claude posts in the thread:

> Claude couldn't clone a repository for this session. Mention Claude in this thread to retry.

**What it means**

The 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.

**How to resolve**

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).

Cut at 300 lines.