"Claude isn't responding," "I suddenly hit a limit," "I can't log in" — even on the same screen, the exact message you see tells you the real cause and fix. This guide breaks down the most common Claude error and warning messages by type, explaining why each one appears and how to resolve it, based on Anthropic's official guidance.
1. Usage limit warnings and errors ("5-hour limit")
Claude enforces usage limits within a five-hour session window that varies by plan. As you approach the limit, a warning appears first: "Approaching 5-hour limit." Once you hit the limit, a blocking message appears with the reset time so you know when you can use Claude again: "5-hour limit reached - resets [time]."
Paid users who have usage credits enabled in Usage settings see a slightly different message: "5-hour limit resets [time] - continuing with usage credits." This only appears for members with access to usage credits.
The fix is straightforward: wait until the displayed reset time, or upgrade to a higher plan. For habits that help you hit limits less often, see reducing Claude usage; for how limits work per plan, see the usage limits guide.
2. Length limit errors ("exceeds the length limit")
You'll see a length limit error when a single message exceeds the maximum input length allowed for the chat: "Your message will exceed the length limit for this chat. Try attaching fewer or smaller files or starting a new conversation." It means the message is too long and must be shortened before sending.
According to official guidance, paid-plan users with code execution enabled have long conversations managed automatically: Claude summarizes earlier messages as context limits approach. As a result, most users rarely hit this error in normal use. Your full chat history is preserved, so Claude can still reference earlier content after summarization.
In the rare cases you still encounter it (for example, sending a very large first message), you can:
- Break content into smaller chunks and process them separately
- Summarize or extract key sections before sending
- Ask Claude to first identify the most relevant portions of your content
- Start a new conversation
Slower or cut-off replies in very long chats stem from the same root (a long context). To understand how tokens and the context window work, see the context window and tokens guide.
3. Capacity constraints — "temporary load"
This message looks alarming but is not an outage: "Due to unexpected capacity constraints, Claude is unable to respond to your message. Please try again soon."
Per official guidance, capacity constraints are normal load management when system-wide demand is high. The system is functioning normally and these issues typically resolve within minutes as demand patterns shift throughout the day. If you see this message, just try again in a few minutes.
Important: Capacity constraints are not technical problems, so they do not appear on the status page (status.claude.com). Seeing this message while the status page shows no issues is expected.
4. Login errors
If a generic error appears when logging in (e.g., "There was an error logging you in"), follow the official steps in order:
- Turn off your VPN. Avoid using a VPN when accessing Claude.
- Disable browser extensions. Active extensions can interfere.
- Clear your browser's cache and cookies.
If the error persists, check the status page (status.claude.com) for active incidents. For broader access and login issues, see Claude not working — troubleshooting.
5. Service incidents vs. capacity constraints
Service incidents are real technical problems where Claude is unavailable or significantly degraded for all or most users. Confirmed incidents are posted on status.claude.com with real-time updates on scope, impact, and resolution. Unlike capacity constraints, incidents do appear on the status page.
Summary: quick response by message
- "5-hour limit" → wait until reset, or upgrade your plan
- "length limit exceeded" → split/summarize content, or start a new chat
- "capacity constraints" → not an outage, retry in a few minutes
- "login error" → turn off VPN → disable extensions → clear cache/cookies → check status page
- Many users affected at once → check status.claude.com for incidents
The error wording and resolution steps in this article are based on Anthropic's official Help Center article "Troubleshoot Claude error messages." On-screen wording may vary by language setting and product updates.