{"version":"2.1.257","anchor":"artifact-publish-retries-once-after-a-stranded-503-on-deploy","canonical_anchor":"artifact-publish-retries-once-after-a-stranded-503-on-deploy","heading":"Artifact publish retries once after a stranded 503 on deploy\/direct","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/artifact-publish-retries-once-after-a-stranded-503-on-deploy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Artifact publish retries once after a stranded 503 on deploy\/direct\n\nA publish whose deploy call returns 503 after the slug is known now waits and retries against that slug.\n\nIf a deploy commit succeeds but the immediate `\/deploy\/direct` response comes back `503` after the slug is already known, the client now waits and retries against that known slug instead of failing the publish outright. The retry is logged via a new `deploy_stranded_retried` telemetry event.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}