{"version":"2.1.277","anchor":"artifact-publish-now-handles-server-rate-limiting-explicitly","canonical_anchor":"artifact-publish-now-handles-server-rate-limiting-explicitly","heading":"Artifact publish now handles server rate limiting explicitly during upload\/copy","tier":"notice","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifact-publish-now-handles-server-rate-limiting-explicitly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact publish now handles server rate limiting explicitly during upload\/copy\n\nArtifact publish now handles server rate-limit responses explicitly during upload and copy, showing a retry-after time\n\n**What**\n\nWhen publishing an artifact, the file-upload and cross-artifact-copy steps now specifically detect a rate-limited response from the server and call a dedicated handler for it, instead of treating it as a generic 'upload unavailable' error. The final error message shown for a failed deploy now includes a `retryAfter` value read from the server's response headers.\n\n**Why**\n\nThis means that if artifact publishing is rate-limited by the server, you now get a clearer error that tells you when to retry, rather than a generic failure message.\n\n- Area: Artifact Publish\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}