Nothing to try yetTier: how much it should matter to you
1Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
API RequestsArea: what it touches
In DevelopmentKind: in v2.1.323,
In DevelopmentSection of the release
Unclear What the overload handling does differently from a normal retry is not stated.
What
When the server answers with an error that Claude Code classes as overloaded, Claude Code retries the request. A new server-side switch changes the first retry. With the switch on, that first retry is not handled as an overload. Later retries, or any retry with the switch off, are handled as an overload as before.
Why
On accounts where the switch is on, the first retry after an overloaded error behaves differently.
Read from
Feature flag
tengu_groovy_rainOff in both readings
The flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.323: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
