{"version":"2.1.225","anchor":"artifact-deploy-retries-429-and-503-responses","canonical_anchor":"artifact-deploy-retries-429-and-503-responses","heading":"Artifact deploy retries 429 and 503 responses","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/artifact-deploy-retries-429-and-503-responses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Artifact deploy retries 429 and 503 responses\n\nArtifact deploys now retry when the server is rate limited or unavailable, and abort cancels retries.\n\n**What**\n\nThe `\/deploy\/direct` call now retries transient server responses instead of failing the deploy outright.\n\n**Details**\n\n- 429 honours the retry-after header, capped at 30s.\n- 503 retries with jittered exponential backoff up to a maximum attempt count.\n- Each retry is logged, and a telemetry event records the attempt count and final status.\n- A user abort cancels the retry loop.\n\n**Evidence**\n\n`deploy_503_retried`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}