What This Error Means
Claude's "something went wrong" is a catch-all error that appears when something fails in a way that is not categorized more specifically. It covers temporary server issues, browser session problems, connection drops, and occasionally specific content that triggers a processing error.
Most occurrences are brief and resolve on their own or with a simple fix.
Step-by-Step Fix
1. Check Anthropic's Status
Go to status.anthropic.com before troubleshooting locally. If Anthropic's services are degraded or experiencing an incident, wait for them to resolve it. This page is updated quickly during outages.
2. Refresh and Retry
Press Ctrl+Shift+R (Cmd+Shift+R on Mac) for a hard refresh. For intermittent errors, this is often enough to get a fresh connection and retry successfully.
3. Sign Out and Back In
- Click your avatar in the top right corner of Claude
- Select Log out
- Close all Claude tabs
- Wait 30 seconds
- Go to claude.ai and sign back in
- Start a new conversation to test
4. Open Claude in a Private Window
Open an incognito or private window and go to claude.ai. Sign in and try sending a message.
- If it works in private mode → an extension or cached data is causing the issue
- If it still fails → the problem is your account session or Anthropic's servers
5. Clear Cookies for claude.ai
- Go to your browser settings → Privacy → Cookies
- Search for claude.ai and anthropic.com
- Delete all stored data for these domains
- Restart your browser and sign back in
6. Start a New Conversation
If the error only happens in one specific chat:
- Click New conversation in the sidebar
- Continue your work in the fresh conversation
- Copy any needed context from the old chat by reading its history
Very long conversations with extensive file uploads are most prone to individual-conversation errors.
7. Try a Different Browser
Test Claude in Firefox, Edge, or Safari if Chrome is failing. Browser-specific extension or rendering issues occasionally cause errors limited to one browser.
8. Disable Extensions
Browser extensions — especially those modifying network requests or injecting scripts — can interfere with Claude's error handling. Disable all extensions in your browser and reload Claude.
Common Mistakes to Avoid
- Sending the same message repeatedly — If a specific message is triggering a processing error (very long prompt, unusual formatting, specific content), resending it will fail the same way. Try a shorter rephrased version.
- Ignoring file size and format limits — If the error appears after uploading, check the file size and format before troubleshooting anything else.
- Not testing in incognito first — Incognito is the fastest way to rule out browser-specific causes. Many users skip this step and spend time on unnecessary troubleshooting.
- Waiting too long without checking status.anthropic.com — During incidents, the error can persist for minutes to hours. Checking status first saves time.
Checking Anthropic's Incident History
If you want to see whether Claude has had recent outages, check status.anthropic.com and look at the incident history. Anthropic posts all significant service disruptions there with timestamps. This is useful for understanding if an error you experienced yesterday was a platform-wide issue or something specific to your setup.
For real-time community reports during outages, developers often post on Twitter/X using #Claude or on the Anthropic Discord — these sometimes surface faster than the official status page during the first few minutes of a new incident.
Claude-Specific Error Patterns
A few error patterns are unique to Claude compared to other AI tools:
During long conversations: Claude's context window has a limit. Very long conversations start producing errors as they approach the limit. The fix is to start a new conversation and summarize the previous context in your first message.
With Projects: If you use Claude's Projects feature and the error appears inside a project, try opening the same conversation outside the project to see if the error follows the conversation or the project settings.
With uploaded files: Claude processes files at the time of upload. If a file was uploaded successfully but the error appears when you reference it, the file may not have been parsed correctly. Re-upload the file and retry.
Claude API vs Claude.ai: Different Error Handling
If you are using Claude through the API rather than claude.ai, "something went wrong" style errors appear as HTTP status codes instead of UI messages. A 500 error means a server-side issue; a 529 means Claude is overloaded. The API includes a error.type field in the JSON response body that gives more detail than the generic UI message. Retry logic with exponential backoff is the recommended approach for transient API errors.
Quick Reference: Fix by Symptom
| When it happens | Likely cause | Fix | |-----------------|-------------|-----| | Every message | Corrupted session token | Sign out, clear cookies, sign in | | One conversation only | Conversation data error | Start a new chat | | After file upload | File size or format issue | Use a smaller or supported file | | Intermittently | Server load | Wait a few minutes and retry | | After Claude update | Session invalidated by update | Sign out and back in |
Related Articles
FAQ
Q: Why does "something went wrong" appear on every single message in one conversation but not others? When the error occurs on every message in one specific conversation but not new conversations, the conversation itself likely has corrupted data — possibly from a failed file upload or a partially delivered message that left the thread in a bad state. Start a new conversation; there is no way to repair a corrupted thread. If you need the content from that conversation, open it and copy the text before abandoning it.
Q: Is there a way to tell if the error is on Anthropic's side or mine? Yes. Check status.anthropic.com first — if there is an active incident, wait for resolution. If status shows all systems normal, test in a new incognito window without extensions. If the error disappears in incognito, the cause is local (extension or cookie issue). If the error persists in incognito across different networks, it is more likely an account-specific server issue and worth reporting to support.
Q: Will I lose my conversation history when this error occurs? No. Conversation history is stored on Anthropic's servers, not in your browser. Even if you sign out, clear cookies, and sign back in, your conversation history remains intact. The error affects the ability to send new messages, not historical data.
Q: How long should I wait before retrying if the error is server-side? For intermittent server-side errors, waiting 5–10 minutes is usually sufficient for minor spikes. For broader incidents visible on the status page, resolution times vary — minor incidents typically resolve within 30–60 minutes; larger incidents may take several hours. The status page shows estimated resolution times when available.
Q: Does the "something went wrong" error affect my usage quota? Messages that result in an error before Claude generates a response do not typically consume your usage quota. If you sent a message and received this error instead of a reply, you generally have not lost any of your message allocation for that period.
Prevention Tips
- Keep a browser tab with status.anthropic.com bookmarked to quickly rule out server-side issues
- If an error appears in one conversation, test a new conversation immediately — this narrows down whether it is thread-specific or account-wide
- Keep conversations focused and avoid very large file uploads to reduce the risk of conversation corruption