{"version":"2.1.225","anchor":"artifact-publish-now-retries-503s-with-a-visible-progress-li","canonical_anchor":"artifact-publish-now-retries-503s-with-a-visible-progress-li","heading":"Artifact publish now retries 503s with a visible progress line","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/artifact-publish-now-retries-503s-with-a-visible-progress-li","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Artifact publish now retries 503s with a visible progress line\n\nPublishing an artifact now retries when the service is busy and tells you it is waiting.\n\n**What**\n\nPublish and deploy calls go through a shared retry wrapper that retries HTTP 503 using a delay derived from retry-after, and the transcript shows why it is waiting instead of appearing to hang.\n\n**Details**\n\n- Retry progress is reported as an `artifact_publish_retry` event, rendered by a new UI component.\n- The line reads \"Publish service temporarily unavailable\" for a 503 and \"Publish service busy\" otherwise, followed by an attempt counter.\n- Telemetry records \"deploy_503_retried\" and \"deploy_429_retried\" with a `deploy_attempts` field.\n\n**Evidence**\n\n`Publish service temporarily unavailable`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}