When using Claude, if you encounter send failures, endless loading spinners, or 403/429 prompts, it’s usually not that it “suddenly broke,” but that limits were triggered by your network, session, or call frequency. Below, based on the most common error symptoms, I’ll clearly lay out the troubleshooting order and actionable fix steps for Claude to help you avoid detours.
First, distinguish whether it’s a Claude service issue or an issue with your environment
Don’t rush to refresh repeatedly as the first step—first determine where the problem is: open Claude’s status page (if you can access it) or switch to another network/mobile hotspot and try again. Then log in to Claude in an incognito window. If it works in incognito but not in a normal window, it’s usually a cache, cookie, or extension conflict.
If the same account is unstable across different devices, while other websites on the same network work fine, prioritize considering temporary congestion on Claude’s side or regional routing jitter. In that case, the most effective approach is to wait a few minutes and try again, and avoid submitting multiple messages in quick succession.
Encountering 429 rate limiting: how to handle too many requests and “send failed”
When Claude shows 429, it’s mostly because requests are too frequent in a short time, a single input is too long, or frequent retries trigger rate limiting. Split a long one-shot instruction into two or three parts, reduce rapid-fire sending, and wait a short while before sending again—the success rate will improve noticeably.
Also, don’t keep hammering “retry” on the same failed message—Claude may treat each retry as a new request. A more reliable approach is to start a new chat, send a condensed version of the core content first, and then gradually add context.
