{"version":"2.1.280","anchor":"artifact-429-retry-now-skipped-when-retry-after-exceeds-a-ca","canonical_anchor":"artifact-429-retry-now-skipped-when-retry-after-exceeds-a-ca","heading":"Artifact 429 retry now skipped when retry-after exceeds a cap","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/artifact-429-retry-now-skipped-when-retry-after-exceeds-a-ca","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Artifact 429 retry now skipped when retry-after exceeds a cap\n\nArtifact upload no longer retries a 429 error if the server's suggested wait time is too long\n\n**Unclear.** The exact threshold value and what happens after the immediate return (e.g. whether the upload is reported as failed) aren't stated.\n\n**What**\n\nWhen an artifact upload gets rejected with a 429 error (\"too many requests\"), the server can include a `retry-after` header telling Claude Code how long to wait before trying again. Previously, Claude Code always retried, capping that wait at 30000 milliseconds even if the server asked for longer. Now, a new helper only returns the server's suggested delay if it's under a set threshold; if the server asks for a longer wait, Claude Code gives up and returns immediately instead of retrying.\n\n**Why**\n\nThis avoids Claude Code sitting around retrying an upload when the server has signaled it needs a long cooldown, failing faster instead of blocking on a lengthy wait.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}