Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.277 ·

Relay now respects Retry-After on busy 503s instead of treating them as hard errors

Busy 503 responses from the relay now trigger a retry after the server's suggested delay instead of failing outright

You'll notice Bug Fixes
JSON All of v2.1.277
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Artifact PublishArea: what it touches
Bug FixesKind: in v2.1.277,
Bug FixesSection of the release
What

When a request to the artifact-frame relay gets back an HTTP 503 ("service busy") response, Claude Code now checks for a Retry-After header telling it how long to wait. If that header is present, the request is routed back through the relay with that delay applied, and a new telemetry event called relay_busy is logged. Previously, this kind of 503 was simply treated as a relay error and not retried.

Why

This lets Claude Code recover automatically from a temporarily busy relay instead of surfacing it as a hard failure.

See this entry in the whole of v2.1.277 →

Feedback