Troubleshooting · Zed

Zed: 529 Overloaded From Claude — What To Do

Zed shows the Anthropic 529 Overloaded verbatim when upstream capacity is saturated. Why your settings are not the cause and what to do while it lasts.

What you see

HTTP 529
{"type":"error","error":{"type":"overloaded_error","message":"Overloaded"}}

Why it happens

  • Upstream capacity is temporarily saturated. The 529 describes the service, not your request or your Zed configuration.
  • It clusters during incidents and peak hours, then clears with no change on your side.

How to fix it

  • Retry after a short pause — the identical request typically succeeds once capacity recovers.
  • For work that cannot wait, switch the thread to a smaller model temporarily; smaller models are generally less contended.
  • Resist reconfiguring: api_url and key changes cannot fix a capacity condition and usually introduce a real error on top.

Related searches

  • zed claude overloaded
  • zed 529 error

FAQ

Did my Zed configuration cause the 529?+
No. Overloaded is a service-side condition passed through verbatim. If your setup produced errors, they would be 401s or 404s, not 529s.
How long does a 529 episode last?+
Usually minutes. If it persists, check the provider's status page rather than editing settings.
Is 529 the same as 429?+
No — 429 is your own throughput ceiling, 529 is upstream capacity. Only the 429 responds to reducing your usage.

All Zed errors · Claude API error codes · Setup guide

Skip the broken setup

apiToken.sale serves the standard Anthropic API — same models, same SDKs, one prepaid balance. Point your tool's base URL at it, and the config on this page works as written.

Get a keyAPI docs