Claude Code v2.1.225 ·
Artifact deploy retries 429 and 503 responses
Artifact deploys now retry when the server is rate limited or unavailable, and abort cancels retries.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.225,
ImprovementsSection of the release
What
The /deploy/direct call now retries transient server responses instead of failing the deploy outright.
Details
- 429 honours the retry-after header, capped at 30s.
- 503 retries with jittered exponential backoff up to a maximum attempt count.
- Each retry is logged, and a telemetry event records the attempt count and final status.
- A user abort cancels the retry loop.
Evidence
deploy_503_retried
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.225 →
