Claude Troubleshooting: Fixing Messages Stuck Spinning/Not Sending, Attachment Parsing Failures, and Lost Conversations

When using Claude, the most infuriating thing isn’t slow answers, but “can’t send, endless spinning, attachments won’t load, conversations suddenly disappear.” This article follows the most common failure paths to clearly lay out the troubleshooting order and actionable fixes, so you can avoid detours as much as possible.

Don’t rush to reinstall: locate the issue via the shortest path

When troubleshooting Claude, the first step is to read the prompt carefully: is it “Send failed,” “Parsing failed,” or is the page unresponsive? Then try reproducing it once in a new chat with the same text to determine whether that conversation is corrupted or the site is having a broader outage.

At the same time, switch your network once: change from Wi‑Fi to a mobile hotspot, or vice versa. Many Claude issues are actually intermittent failures caused by network jitter, DNS anomalies, or corporate proxies.

Messages stuck spinning / send failed: prioritize the browser and network

If Claude keeps spinning, refresh the page and wait for it to reconnect; if it recurs frequently, clear the site’s cache and cookies and log in again. Then temporarily disable browser extensions (especially ad blockers, script managers, and privacy/security tools)—these plugins often block Claude’s requests.

If Claude works on your phone but not on your computer on the same network, it’s usually a computer browser environment issue; if it’s the other way around, it’s more likely a network or ISP routing problem. When troubleshooting Claude, don’t fixate only on the account—eliminate environmental variables first.

Attachment uploads but “can’t be read”: usually a format, content, or parsing limit

Common reasons for Claude attachment parsing failures include encryption, permission restrictions, scanned image–based PDFs, or content that’s too complex and causes parsing to abort. The most reliable approach is to “Save As” the PDF to a new file, remove password protection, or export key pages as images and try again.

Also, special characters in the filename, overly long paths, or uploading multiple attachments at once can trigger parsing issues in Claude. When troubleshooting, use a short filename, upload only one attachment at a time, and explicitly tell Claude in your message “which pages/which section to focus on.”

Conversation content missing / reset: first confirm whether it’s a display issue

If a Claude conversation looks like it’s “gone,” sometimes it’s just the frontend failing to load it. Try logging in via an incognito window to check; if it works in incognito, it indicates a local cache or extension–caused display issue—clearing cache and disabling extensions as mentioned above usually restores it.

If the conversation gets reset midway, break long tasks into smaller chunks and submit them step by step, and at each step have Claude restate the completed key points as a “checkpoint.” This can significantly reduce the cost of troubleshooting and also prevent rework.

Still not solved: how to provide useful feedback and work around it temporarily

When Claude keeps throwing errors, the most useful feedback includes: the exact error message, the network environment at the time, browser version, whether an attachment was involved, and the shortest reproducible steps. Sending only “it doesn’t work” basically won’t lead to effective diagnosis.

There are also standard temporary workarounds: copy your input into a new chat, convert attachments to plain text excerpts of the key sections, or switch to another browser/device to finish the current task. The goal of troubleshooting Claude isn’t to “find every cause,” but to restore usability as quickly as possible.