[Bug] Anthropic API Error: 529 Overload Response

Status Fixed / completed
Reported on v2.1.220
Maintainer reply None cached
Activity 0 comments · opened Jul 30, 2026 · closed Jul 30, 2026

Bug Description
Repeated 529 overloaded_error responses over the past several sessions, not rare. Tonight alone: 6 episodes between 05:03–06:07, 2 of which exhausted all 11 retries and killed the turn. Separately, a distinct bug: a Connection error. with zero HTTP status (fails ~130–250ms after dispatch, on a reused keep-alive socket) hits ~10.6% of commands, up to 33% on bad sessions — always self-recovers by retry 3, but happens on nearly every session, 439 occurrences across 15 sessions over 11 days. Client version 2.1.220 stopped recording these to session transcripts even though the debug log still shows them — that's a separate regression worth flagging on its own. Terminal request ID from tonight's worst episode: req_011CdXjtEg8TzLFMKUgy4b17.

View original on GitHub ↗