›_ Claude Code Issues
Claude Code Issues / Error strings / API Error 429 (rate_limit_error) / Page 2

API Error 429 (rate_limit_error) — page 2

The API rejected the request for exceeding a rate or usage limit.

690 issues · 23 open · 667 resolved (97%) · first seen Mar 28, 2025

First response · account

What to do now

Most likely: The account, organization or endpoint exceeded a rate or usage window.

  1. Stop parallel retries and wait for the response’s retry window.
  2. Check current usage, plan limits and whether another process shares the same credentials.
  3. Use bounded exponential backoff; changing prompts does not reset a rate limit.

These are conservative triage steps, not an official Anthropic fix. Use the issue and workaround evidence below before making a destructive configuration change.

Is this getting better or worse?

This class of problem is converging. 166 new reports in the last 90 days vs 329 in the 90 before — -50%. The open backlog peaked at 125 in 2026-04 and sits at 23 today.

0 31 63 94 125 2025-032025-092026-032026-08
2025-03 — First reports2026-04 — Peak backlog (125 open)

Derived by counting each matching issue from its creation date until it closed. First-party computation over the anthropics/claude-code tracker — the trend is not published anywhere upstream.

Which builds report this

554 of these reports name the Claude Code build they were running, spanning 100 releases. Heaviest reporters:

Report volume, not a defect count: an issue can mention a build without that build having caused the failure. Versions come from the version string in the bug-report template, matched against real published tags.

Do these get fixed?

Median time to close is 20 days across 667 closures. Of the 667 closures with a recorded reason, 9% were closed as completed and 609 as not-planned or duplicate. The most recent completed fix landed in 2026-08.

Workarounds reported by the community

21 of these issues post a workaround someone says worked. The highest-engagement ones:

You've hit your limit · While usage is still at 84%
…got "While our Support team is unable to manually reset or work around usage limits, you can learn about best practices [here]( If you’ve hit a message limit, you’ll need to wait until the reset time, or you can conside…
Found in the thread of #19673 · still open
[BUG] /api/oauth/usage endpoint returns persistent 429 for Claude Max users (retry-after: 0)
Root Cause Found + Workaround After investigating, we discovered that rate limits are per-access-token, not per-account . Each new OAuth access token gets a fresh rate limit window (~5 requests before 429). How to bypass…
Found in the thread of #30930 · still open
[Bug] Anthropic API Error: Usage credits required for 1M context window with opus-plan model
…sn't work, and just stops working at 1M Context. A feasible workaround would be to periodically use the /compact command manually.
Found in the thread of #61869 · resolved
[BUG] Skill `model:` frontmatter triggers 429 "Extra usage required" on 2.1.76 when session uses opus[1m]
…Sonnet promoted to . Rejected if account lacks entitlement. Workarounds - Stay on 2.1.75 — skill model switching works correctly without auto-promotion. Caveat: if a sonnet skill (200K) is invoked from an opus[1m] sessio…
Found in the description of #34296 · still open
[BUG] Rate limit 429 errors despite dashboard showing available quota - Two Max accounts, documented inconsistencies
….3% , meaning ~20x token inflation per turn. After applying workarounds it stabilized at 89-99% . Full analysis with per-request measured data, safe workarounds, and community references (including [cc-cache-fix](
Found in the thread of #22876 · still open

Excerpts are quoted from the linked issue so you can judge relevance before opening it. Threads that only ask for a workaround, or report that there is none, are excluded. These are community suggestions, not official guidance from Anthropic — read the full thread before applying one.

Matching issues 101–200

Ranked by community engagement (reactions weighted over comments). Listing the top 300 of 690 matches; the statistics above cover all 690.

Related aggregations

  1. API Error 400 (invalid_request_error)

    2,591 issues

  2. API Error 500 (internal server error)

    603 issues

  3. API Error 401 (authentication_error)

    441 issues

  4. API Error 529 (overloaded_error)

    254 issues

  5. API Error 403 (permission_error)

    235 issues

  6. API Error 413 (request_too_large)

    38 issues