“Checking for a Response” and “A Previous Response Is Still Running” in Claude: What They Mean and How to Fix Them
Updated November 2026. Claude now often shows a newer line in the same situation: “Checking for a response to your message. If Claude is still working on it, you’ll see it here.” It has its own section below, along with “Claude is busy right now” and the other messages people are seeing this month.
The first time I saw this message, I’ll be honest — I panicked a little. I’d asked Claude for a long report, got impatient, sent a second message… and suddenly it wouldn’t take anything new. Just a calm little line at the bottom: “A previous response is still running in this conversation. It will appear shortly — try again once it finishes.”
Turns out it’s nothing to worry about. If you’re seeing it right now, here’s the short version before we get into the details: Claude is still busy finishing your last reply, so it won’t start a new one yet. Wait a few seconds, refresh, and you’re back. That’s it most of the time.
Seeing a different line, such as “your message was sent, but Claude couldn’t respond” or “this response didn’t load”? Each one has its own section further down, and the table near the end tells them apart. If there is no message at all and Claude has simply gone quiet, slowed down or cut off mid-answer, that is a different problem, covered in our guide to Claude not responding or giving incomplete responses.

So what’s actually going on?
Here’s the thing people miss: inside one chat, Claude can only handle one answer at a time. If you fire off a new message while the previous one is still being written, it doesn’t queue it up or panic — it just pauses you and shows that message.
In plain words, it’s saying: “Give me a second, I’m still writing your last answer.” The moment that earlier reply wraps up, the chat unlocks by itself and you can carry on. That is what separates it from Claude going silent in a very long chat: here the conversation is busy, not overloaded, so waiting actually works.

And no — this isn’t a crash, a ban, or a billing problem. Your message didn’t vanish, and your account is perfectly fine. It just looks scarier than it is. When it happened to me, the reply actually showed up the instant I refreshed the page — so don’t assume the worst.
Why it keeps happening
A few things tend to trigger it, and once you know them they’re easy to dodge:
The most common one is simply a long reply still cooking. Big asks — full reports, chunks of code, heavy research — take longer, so the chat stays “busy” for a while. If you’re regularly pushing Claude with huge prompts, it’s worth learning how to manage session limits and token usage too, since they often go hand in hand.
The second sneaky one is closing the tab mid-reply. The response keeps running in the background, so when you come back the chat still thinks it’s working.
After that it’s the usual suspects: a shaky internet connection that drops the “I’m done” signal, a frozen browser tab that stopped refreshing, or just busy servers during peak hours when everything’s a touch slower.
How to get it working again

Start gentle and work your way down — you’ll rarely need to go past step two.
Just wait about half a minute.
Most of the time the reply just needs a moment. Resist the urge to keep hitting send, because that only re-triggers the same message.
Refresh and reopen the same chat.
Reload Claude, click back into the conversation, and the finished answer is usually sitting right there waiting for you. This is the one that fixed it for me every single time.
Open a fresh tab.
If the page feels frozen, a new tab clears it out. Log back in and check.
Look at your connection.
Flip to a steadier network, or off Wi-Fi and back, then reload.
Try another browser (or incognito).
This rules out a stuck, cached session in seconds.
Still stuck? Start a new chat.
It’s the last resort — you’ll lose the in-progress reply — but you can just paste your prompt again and move on.
How to stop it happening again
Most of this comes down to one habit: let each answer finish before you send the next. That single change fixes it for most people.
Beyond that — break really long requests into smaller messages so they finish faster (a tighter, well-written prompt helps here), don’t slam the tab shut while Claude’s mid-sentence, and use a stable connection when you’re doing something important.
Once Claude’s running smoothly again, you can get back to the fun stuff, like using it to create faceless videos using Claude AI.
“Checking for a response to your message. If Claude is still working on it, you’ll see it here.”
This is the newer wording of the same situation. Claude has your message and is checking whether a reply is still being written for it. You usually see it after you reload or reopen a chat while an answer was in progress, or when your connection dropped partway through a reply.
Do not send the message again. If a reply is still being written, it appears in the same spot once it finishes, and resending only gives Claude the same question twice.
- Give it up to a minute. Long answers, code and research take longer, and this line stays until the reply is ready.
- Reload the conversation once. If the reply finished while you were away, a reload brings it in.
- Still there after a few minutes? Check status.claude.com for an incident, then open a new chat and paste your prompt.
“Claude is busy right now. Try again in a moment.”
This one is about Claude’s capacity, not your conversation. Anthropic is handling more requests than it can take at that moment, so your request was not started. There is nothing running in the background, so there is nothing to wait for.
Wait a minute and send it again. If it keeps happening, check status.claude.com. A busy notice during a known incident usually clears when the incident does.
It is not the same as reaching your usage limit. A usage limit message tells you when you can send again, and retrying sooner will not help.
“Request couldn’t be processed. You can try again.”
Claude could not handle that one request. It is usually a short-lived failure on Anthropic’s side, but it can also come from an attachment Claude cannot read, or a very large file.
- Send it once more. A one-off failure often goes through on the second try.
- Check your attachment. Try again without it, or with a smaller file or a different format, such as a PDF instead of a scanned image.
- If it fails in every chat, check status.claude.com before changing anything else.
“This chat is available in the new Claude experience. Reopen it there to keep going.”
Anthropic has been moving Claude to an updated app experience. When a conversation belongs to the newer version, the older view can still show it but cannot continue it. Your chat is not lost.
Use the reopen link in the message, or open claude.ai in a fresh tab and find the conversation in your chat list. If you use the desktop app, update it to the latest version first, since an older app is the usual reason you land in the old view.
“Your message was sent, but Claude couldn’t respond — try again.”
Claude received your message. What failed was the reply coming back to you, which makes this close to the opposite of the message above.
That difference matters, because the message is already sitting in the conversation. Send it again and you have asked the same thing twice. Look at the chat first: if your prompt is there with nothing underneath it, do not resend yet.
Work through these in order:
- Reload the conversation. If the answer finished on Claude’s side and only the display failed, it shows up after the reload.
- Nudge it instead of resending. If your message is there but still unanswered, type something short like “please answer the message above”. That costs far less than pasting a long prompt again.
- Move to a new chat. A conversation that has failed once often keeps failing. Paste the prompt into a fresh one.
- Check whether it is only you. If every chat fails, the problem is not your conversation. Anthropic publishes live service status at status.claude.com, and it is worth a look before you troubleshoot anything else.
Ad blockers, script blockers, strict privacy settings and some office or campus networks can cut the connection that delivers the reply. If you see this message regularly, run the same prompt once in a private window with extensions switched off. That single test tells you whether the fault is Claude or your browser.
“This response didn’t load.”
Claude wrote a reply. Your browser never displayed it. That is the whole meaning of this message, and it is why a refresh fixes it so often.
Refresh the page and reopen the same conversation before you try anything else. Most of the time the missing answer is already sitting there.
If the chat unlocks after “a previous response is still running” but the earlier answer never appears, reload once more before sending anything new, so you don’t end up asking twice.
If it is still missing after a reload, open the chat in a private window with extensions off. Long answers fail to load more often than short ones, so if one large request keeps failing, ask for it in two or three parts. The full checklist, including what to do when replies stop loading in every chat, is in Claude response not loading.
“Your previous message wasn’t sent. You can try again.”
Claude never received this message, so there is nothing waiting to arrive and nothing to duplicate. It is the one message on this page where resending really is the right move.
Send it again. If it fails a second time, the cause is usually on your side rather than Claude’s:
- Check you are still signed in. An expired session often shows up as a message that simply will not send.
- Reload the page, then send it again.
- Switch off a VPN or proxy and retry.
- Shorten it. Very long prompts and large attachments can fail to upload on a slow connection. If a short version goes through, size was the problem.
Keep the two straight, because the right move is different for each. “Wasn’t sent” means send it again. “Was sent, but Claude couldn’t respond” means reload and wait, or you end up asking twice.
“Claude is responding in the background”
Claude is still writing your answer while the tab sits in the background or you are looking at something else. It is a status note, not an error.
Leave the tab open and let it finish. Come back to the conversation and the reply is normally there.
Where it gets stuck is when the tab was closed or the device went to sleep partway through the answer. If the notice is still showing after a few minutes and nothing new has appeared, reload the chat. That forces the interface to go and check what actually finished.
“Claude finished the response” but nothing appeared
Claude has marked the answer complete and the screen has not caught up. It is the same underlying problem as a response that didn’t load, so the same fix works: reload the conversation.
If the answer still comes back empty after a reload, it did not survive. Ask for it again in the same chat, and if the request was a big one, ask for the first section only. A shorter answer has less that can go wrong.
“Claude couldn’t finish this response. Try again in a moment.”
Claude started the reply and stopped before the end. That is truncation, not a connection failure, and it is worth handling differently.
Do not resend the original prompt, because that makes Claude start over. Ask it to carry on from where it stopped, and paste the last line or two it produced so it knows the exact seam.
If it keeps stopping, the conversation is usually carrying too much. Our guide covers what to do when Claude will not continue a response, including when to move the work to a fresh chat.
Which message are you seeing?
| Message | What it means | First thing to do |
|---|---|---|
| Checking for a response to your message | Claude has your message and is checking on the reply | Wait up to a minute, then reload. Don’t resend |
| Claude is busy right now. Try again in a moment | Claude is at capacity for a moment | Wait a minute and retry, check the status page |
| Request couldn’t be processed | That single request failed | Send once more, remove or shrink attachments |
| This chat is available in the new Claude experience | The chat belongs to the newer app | Reopen it from the link, or update the app |
| A previous response is still running in this conversation | Your last reply is still being written | Wait, then reload the chat |
| Your message was sent, but Claude couldn’t respond | Claude received it, the reply failed on the way back | Reload first, do not resend straight away |
| Your previous message wasn’t sent | The message never reached Claude | Send it again |
| This response didn’t load | The reply exists, the page never rendered it | Refresh, then try a private window |
| Claude is responding in the background | Still being written while the tab is not in focus | Leave the tab open and come back |
| Claude finished the response | Marked done, the screen did not update | Reload the conversation |
| Claude couldn’t finish this response | The answer stopped partway | Ask it to continue from the last line |
If Claude’s acting up in other ways
These cover the other problems people run into:
- Claude Not Responding, Slow or Response Incomplete? Fixes by Symptom
- How to Fix Claude Session Limits and Reduce Token Usage
- Claude Cowork Not Working? 9 Common Problems and Fixes
- MCP “Failed to Connect”: Fix Every Error Message
- Free AI Prompt Optimizer & Checker: Fix Weak Prompts
And to put Claude to work for your business, explore our free AI tools for business.
Quick questions people ask
Is “a previous response is still running” an error or a bug?
Neither. It’s just a status note saying Claude’s still finishing your last reply. Nothing’s broken.
Did I lose the message I tried to send?
Nope. Once the earlier reply finishes you can send it. And if you start a new chat, just paste it again.
How long does “a previous response is still running” take to clear?
Usually seconds — under a minute. Longer answers (big reports, code) take a bit more.
It has been several minutes and Claude is still stuck. Now what?
Refresh, then try a new tab. If it still won’t budge, open a fresh conversation and resend.
Is “your message was sent, but Claude couldn’t respond” the same thing?
No, and the fix is different. That one means Claude got your message and the reply failed on the way back, so your prompt is already in the chat. Reload before you resend, or you will have asked twice.
So when should I actually resend?
Only when Claude tells you your previous message wasn’t sent. For every other message on this page, reload the conversation first.
Why do I keep seeing different messages for what looks like the same problem?
Because they are different failures. One is Claude still writing, one is a reply that never arrived, one is a message that never sent. The table above separates them.
What does “Checking for a response to your message” mean in Claude?
Claude has your message and is checking whether a reply is still being written. Wait up to a minute and reload once. Don’t resend, or you’ll ask the same thing twice.
Is “Claude is busy right now” the same as hitting my usage limit?
No. “Busy” means Claude is at capacity for a moment, and retrying a minute later usually works. A usage limit message tells you when your allowance resets.
Done for you
Running your business on Claude?
We connect Claude to your CRM, inbox and docs through the API, so your team gets reliable answers without chat-app limits.
