Skip to main content
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. 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).
  2. Is Claude in this channel? Type /invite @Claude. 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).
If @Claude still gets no reaction and no reply after all three, send your admin the admin entries for a silent workspace. 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, 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.
  • A message about permissions or access: your organization restricts who can use Claude; send your admin the member access setting.

​
Claude reacted to my message but never replied

What you see Claude added a reaction to your message, but no reply arrived. What it means A reaction 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 neither helps, start a new thread and restate the request. Each thread is backed by its own session, and a fresh thread gets a fresh one.

​
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. In a channel shared across workspaces inside your Enterprise Grid, you may instead see “This channel is shared across multiple workspaces, and Claude can’t verify whether it includes guests, so Claude can’t respond here” or “This channel is shared among several Claude workspaces, so Claude cannot respond here.” Both mean the channel spans more than one workspace; the admin entries on these messages explain what causes each one and which, if either, an admin setting 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.

​
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. If you don’t know who your organization’s owners are, ask whoever set Claude up in your workspace.
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 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 every case the work isn’t lost; the same thread picks up where it stopped.

​
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 in Slack 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.

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

​
Lost or stale work

​
Claude lost work it created earlier

What you see Claude can’t find files or drafts it made earlier in the thread. What it means The isolated workspace where Claude works on a thread is recycled after a period of inactivity. Work that was pushed to a branch, opened as a pull request, or posted into the thread survives. Files that existed only inside that workspace don’t, and Claude will need to recreate them. How to resolve Ask Claude to recreate the file, and for long-running work, ask it to commit and push early, or to post drafts into the thread as it goes, so nothing lives only in that workspace. The definition-of-done habit helps here. Make “push the branch” or “post the file” part of the task.

​
My old thread stopped working, but new threads are fine

What you see A thread created a while ago fails the same way on every retry, while new threads work. What it means Each thread keeps the configuration it started with, so a thread created weeks ago can stop working after your organization’s setup changes, even though new threads work. Retrying in the same thread will usually keep failing the same way. How to resolve Start a new thread and restate your request; paste a link to the old thread so Claude picks up the context.

​
Claude picked the wrong repository

What you see Claude started working in a repository you didn’t mean. What it means The request didn’t name a repository, so Claude picked one from the channel’s grants. How to resolve Start a new thread with the right one named in your first message, for example “in acme/data-pipeline, fix the failing import.” Naming the repository up front is also how you prevent this. If you need another repository mid-thread, ask Claude to add it (“add acme/data-pipeline”) and confirm with the Confirm button it posts; if the repository isn’t allowed for this channel, Claude tells you after you confirm.

​
Claude forgot instructions I gave it before

What you see Something you told Claude earlier doesn’t stick in later threads. What it means Channel memory is a small, curated note, not a transcript, and Claude decides what’s worth saving, so passing details usually aren’t kept. How to resolve To make an instruction stick, say so explicitly, as in remember for this channel: always post reports as a table. Keep saved instructions short; the per-channel memory budget is limited, and long entries crowd out everything else. For longer playbooks, store them in a repository Claude can read. Verify what stuck by asking what it remembers about the channel. See What Claude Tag remembers.

​
Access and connections

​
A connection my admin added isn’t showing up

What you see Your admin added a connection, and Claude in your thread says it doesn’t have it. What it means A session loads its connections when it starts, so an existing thread keeps the set it started with. Scheduled jobs work the same way; a job keeps the connections that existed when it was created. How to resolve Start a new thread to pick up the new connection. For a scheduled job, edit or recreate the schedule. If the fix worked, asking @Claude what can you access from this channel? in the new thread lists the connection.

​
Claude says it can’t access a channel it read before

What you see One reply surfaces findings from a channel, and a later one says “I can’t access that channel.” What it means This usually doesn’t mean access changed. Claude can search public channels it isn’t a member of, but it can’t read one directly without being invited, so search results and direct reads come and go differently. How to resolve If it needs to read a channel directly, invite it with /invite @Claude in that channel, then ask again in a new thread.

​
Claude says it can’t reach a tool or service

What you see Claude says it has no connection for a service you expected it to reach. What it means The channel likely hasn’t been given a connection for that service; see what each connection adds. How to resolve Ask your admin to add one for this channel and send them the connection scope entry. Once they have, start a new thread; a session loads its connections when it starts. If the fix worked, asking @Claude what can you access from this channel? in the new thread lists the service.

​
Claude can’t connect over SSH

What you see Claude reports it can’t reach a host over SSH, or a database’s native protocol times out. What it means Every request Claude makes from a channel passes through Agent Proxy, which carries HTTP and HTTPS only. A protocol that isn’t HTTP, such as SSH or a database’s native wire protocol, can’t cross the proxy to any host, so this isn’t a connection your admin can add. How to resolve If the service exposes an HTTP API, ask your admin to add a connection for that instead.

​
You’ve reached a Claude in Slack spend limit

What you see Claude posts in the thread:
You’ve reached a Claude in Slack spend limit. Org admins 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 in Slack spend limit.” for the organization limit, or “Heads up — this channel has used N% of its monthly Claude in Slack 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. How to resolve Ask your admin to raise the limit; they do so at claude.ai/admin-settings/usage/claude-in-slack. Your admin here is whoever manages your organization’s Claude account at claude.ai, not necessarily your Slack administrator. Once the limit is raised, mention Claude in the same thread to retry.

​
DMs aren’t working

DMs run on your own Claude account rather than the organization’s agent. They need a seat that includes Claude Code, and they use your personal connectors rather than the channel connections. If channels work but DMs don’t, first check that your Claude account is connected; DM @Claude and it prompts you to connect if it isn’t.

​
I get an environment error in a DM

What you see Claude replies in the DM:
I couldn’t find a Claude Code environment for your account. Set one up at claude.ai/code and try again.
What it means DMs run on your own claude.ai account rather than the organization’s setup, which is why this appears there and not in channels. It’s usually a brief lookup failure rather than a missing environment. How to resolve
  1. Mention Claude again; the retry usually clears it.
  2. If it keeps happening, the environment your account is set to use may no longer be available; check it at claude.ai/code.
If a channel (not a DM) shows session-start failures that mention an environment, send your admin the environment scope entry.

​
Your Claude account is connected, but it doesn’t have access in this organization

What you see 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.
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. What it means Your seat type doesn’t include the Claude Code engine that powers DMs. Mentioning @Claude in a real channel doesn’t depend on your seat type and keeps working. How to resolve Channels keep working while you wait, so mention @Claude there if you need an answer now. Then ask your admin (whoever manages your organization’s Claude account at claude.ai) about your seat assignment; the admin entry on this message covers the fix.

​
Your Claude admin has disabled sending direct messages to Claude

What you see Claude replies when you DM it:
Your Claude admin has disabled sending direct messages to Claude.
What it means DMs are turned off organization-wide. How to resolve Use a channel instead, or ask your admin about enabling DMs.

​
Group DMs aren’t supported

What you see Claude replies in the group DM:
Group DMs aren’t supported. Try a channel or a 1:1 DM instead.
What it means Claude works in channels and one-to-one DMs only. How to resolve Start a private channel with the same members instead.