Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.1.225 Home All releases olderv2.1.224 v2.1.226newer

Artifact deploy retries 429 and 503 responses

You'll notice
Useful3 Signal0
Artifacts

Artifact deploys now retry when the server is rate limited or unavailable, and abort cancels retries.

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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →