Sometimes Claude stops mid-answer and shows "Your previous message wasn't sent. You can try again." or "Conversation content temporarily unavailable; please retry." It's jarring, but here's the good news up front: this error is almost always temporary, and the message you typed usually isn't lost. Below is what each message means, the most common causes, and the order in which to troubleshoot.
🟢 Model references match the current lineup · model notice · Fable subscription
Fable 5 and 5.1 subscription (updated September 7, 2026): Claude Fable 5.1, released September 1, 2026, is the current Fable model and Fable 5 is now legacy. Plan terms are the same for both — Max and Team Premium plans include Fable at up to 50% of the weekly usage limit; Pro and Team Standard use usage credits (
What does this message mean?
"Your previous message wasn't sent" means, literally, that your last message didn't reach or wasn't processed by the server (fact — the meaning of the phrase). The request was cut off before Claude received it, so resending the same message usually works.
"Conversation content temporarily unavailable" means the conversation's content couldn't be loaded for a moment (fact — the meaning of the phrase). This points to a temporary problem displaying or loading the conversation data, rather than to sending a message.
Both messages explicitly suggest you "retry," which signals a temporary state that a retry can clear, not a permanent error (inference).
Most common causes (inference)
The causes below aren't each spelled out in official documentation; they're the typical reasons a web service or chat interface shows symptoms like these (inference). The actual cause can vary by setup.
- Temporary server-side issues or an outage: when error rates rise on Anthropic's side (for example, errors on a specific model), these messages are the most common result. There's little you can do except wait for recovery.
- Unstable network: switching between Wi-Fi and mobile data, weak signal, a VPN/proxy, or a corporate/school firewall can drop the request.
- A very long conversation: when a single conversation grows long and heavy, loading its content is more likely to fail (inference). This tends to produce the "content unavailable" message.
- Browser-side problems: stale cache/cookies, an expired session, ad-blocking or other extensions, or a tab left open too long.
- Large attachments or images: sending a big file alongside your message can cause the upload to fail partway.
First check: just you, or a full outage?
The first thing to do is separate "my problem" from "a Claude-wide outage." Anthropic runs an official status page (fact). If an incident is in progress, no amount of fixing your network or browser will help, so it's better to wait for recovery.
- Official status page: status.claude.com — shows the state of claude.ai, the API, and Claude Code, plus active incidents and maintenance.
- You can also see the same official data summarized on usingclaude.com: Claude Service Status.
If the status page shows something like "Elevated error rate," your symptoms are likely caused by a broader outage (inference).
Step-by-step fixes
If you've confirmed it isn't a full outage (or you can't tell), try these in order. Most issues resolve in the first few steps.
- 1. Wait a moment and retry: click "Try again" on screen, or resend the same message. A brief hiccup is often fixed right here.
- 2. Refresh the page / reopen the conversation: refresh your browser (F5) and reopen the conversation. This is especially effective for the "content unavailable" message.
- 3. Check your network: switch to a different Wi-Fi or mobile data, and turn off any VPN/proxy. On a corporate or school network, a firewall may be blocking it.
- 4. Start a new conversation: if the problem conversation is very long, open a new one and ask the same question. This is the most reliable workaround when length is the cause.
- 5. Clean up the browser: clear cache/cookies, open an incognito/private window, disable ad-blockers and other extensions, or try a different browser.
- 6. Restart/update the app: if you're on the mobile or desktop app, fully quit and relaunch it, and make sure it's the latest version.
- 7. Shorten the message or attachment: if you were sending very long text or a large file, shorten it or split the file.
Two related errors you may also see
Around the same time as the message above, the same conversation can also show one of the two notices below. Both can appear in the desktop app (Windows and macOS) and on the web, and both are usually temporary.
"A previous response is still running in this conversation"
This means Claude is still generating an earlier reply and you sent a new message before it finished. A single conversation generates only one response at a time.
- As the notice says, the earlier reply usually appears shortly, after which you can continue.
- If it seems stuck for a long time, press the stop button in the composer or refresh the conversation, then try again.
- If it still won't clear, fully quit and reopen the app, or start a new conversation with the same message.
"Your message was sent, but Claude couldn't respond"
This means your message reached the server, but generating the reply failed — unlike error #1, where the message never went through. The exact internal cause isn't officially documented; temporary server load or a processing timeout are likely factors.
- Press retry on the notice first. If it was a momentary glitch, the response generates right away.
- If it repeats, wait a moment and try again, or split a very long message into shorter parts.
- If it only happens in one conversation, try the same question in a new one.
Will I lose my message or conversation?
"Your previous message wasn't sent" generally means the message hasn't been sent yet, so you can usually resend the same text. "Conversation content temporarily unavailable" is usually temporary too, and the conversation often reappears after a refresh (inference). Just in case, it's a good habit to copy long messages before sending (practical tip).
When it keeps appearing in the Windows desktop app
If these messages show up in the Claude desktop app for Windows rather than the browser, the cause may be the shared ones (brief network drops, server congestion) or the app’s own state getting stuck (our estimate). Work through these steps to narrow it down quickly.
- Cross-check on the web — open claude.ai in a browser with the same account and send a message. If the web works but the app doesn’t, it’s an app-side issue; if neither works, it’s your network or the service.
- Fully quit and relaunch the app — closing the window does not quit the app. Right-click the Claude icon in the system tray (next to the clock) and choose Quit, then reopen it.
- Check for app updates — the desktop app updates frequently, and send-related issues in older builds are sometimes fixed in newer ones. Check for updates in settings, or install the latest build from the official download page over the top.
- Restart your PC — a reboot is the most reliable way to clear stuck background processes.
For reference, a false-alarm case — the “Your previous message wasn’t sent” toast appearing even after a response rendered completely — has actually been reported in Anthropic’s official GitHub repository (May 2026, desktop app). If the reply is fully visible and the conversation continues, your message was saved, and you can safely ignore the notice.
If it keeps happening
If other symptoms show up too — login, access, or no response — see the full guide to when Claude isn't working.
If it persists after all of the above, check the official status page again; if an incident is listed, give it time and retry. If status looks normal but it keeps failing, you can get help from the official support center (support.claude.com). Including your browser/app, the time it happened, and the exact on-screen wording will speed up diagnosis.
Related articles
- Claude Not Working? Fix Login, Access & Errors (2026)
- Troubleshooting Claude Error Messages: Limits, Capacity, Login
- Claude File Upload FAQ: Formats, 500MB/20-file Limits, PDF Handling
- Claude API Error Handling, Retries & Rate Limits: Complete Guide
- How to Read Claude Code Error Messages — A Beginner's Guide
- Claude 529 Error (Overloaded): What to Do
- Claude Login Email Not Arriving — What to Do When Corporate Filters or Lost Email Access Block You