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.
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.
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).
If it keeps happening
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.