The most annoying things about using Claude are “can’t send,” “stops halfway through a reply,” and “can’t upload attachments.” This article lays out a Claude troubleshooting workflow in the order you’d actually use it: check the server first, then your network and browser, and finally your account and file issues. Follow it and you can usually pinpoint the cause in just a few minutes.
Start with basic troubleshooting: confirm whether it’s a server-side fluctuation
Before you begin troubleshooting, first check whether Claude is unstable overall: open Anthropic’s status page or quickly try again on a different network. If multiple devices at the same time are seeing send failures or endless loading spinners, it’s more likely server congestion—repeatedly refreshing will only make it easier to trigger rate limits.
The conclusion at this step is simple: if the status page shows an incident, wait a bit and try again; if the status is normal, proceed to the local troubleshooting steps below.
Troubleshooting send failures: network, browser, and extensions are the most common
When Claude fails to send, troubleshoot the network first: switch between Wi‑Fi and cellular, disable your proxy or change nodes, and make sure login and requests go through the same network environment. Then troubleshoot the browser: sign in again in an incognito window and clear cache and cookies—many cases of “click send and nothing happens” are due to cache issues or an expired session.
If you have ad blockers, script managers, or privacy extensions installed, temporarily disable them and try again. After an extension blocks a request, the page may look normal, but the message will silently fail to send.


