529 storm at session start kills the session with zero replies instead of backing off
Open 💬 0 comments Opened Jul 7, 2026 by marshallcourchaine-debug
During an API 529 ("Overloaded") storm, a freshly started session retried 9 times in quick succession, got 529 every time, and died having produced zero assistant messages — the user's bug report (with screenshots) got no response at all. A separate long-running session lost a 38-minute subagent's entire output to a single "Server is temporarily limiting requests" error.
Expected: exponential backoff with a longer horizon at session start (nothing is lost by waiting), and subagent results should be checkpointed so a terminal API error surfaces partial work instead of discarding it.
Environment: Claude Code CLI on Windows 11. Observed 2026-06.