{"version":"2.1.277","anchor":"artifact-publishing-gets-dedicated-rate-limit-error-messages","canonical_anchor":"artifact-publishing-gets-dedicated-rate-limit-error-messages","heading":"Artifact publishing now gives clearer errors when rate-limited","tier":"notice","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifact-publishing-gets-dedicated-rate-limit-error-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact publishing now gives clearer errors when rate-limited\n\nPublishing an artifact now shows specific messages when it's rate-limited, including retry timing and which step failed\n\n**What**\n\nThe artifact publish tool now detects and reports rate-limit (HTTP 429) responses at each stage of publishing, preflight and upload alike, using a new response-checking helper. When a 429 is hit, a new message builder reports:\n\n- that nothing was published and the request was rate-limited\n\n- the reserved slug involved\n\n- which step was refused (for example, staging a publish's copied files)\n\n- retry-after-based wait-time information, so the user knows when to try again\n\nA distinct 422 'contract is newer than preferred' handshake message was also added for a separate related failure mode.\n\n**Why**\n\nPreviously a rate-limited or conflicting publish attempt likely surfaced as a generic failure. Now the error clearly explains that nothing was published, why, and when it's safe to retry, making it easier to recover from a failed artifact publish.\n\n- Area: Artifact Publish\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}