{"version":"2.1.238","anchor":"clearer-artifact-publish-failures-including-a-refused-auto-p","canonical_anchor":"clearer-artifact-publish-failures-including-a-refused-auto-p","heading":"Clearer artifact publish failures, including a refused auto-publish","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/clearer-artifact-publish-failures-including-a-refused-auto-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Clearer artifact publish failures, including a refused auto-publish\n\nArtifact publish failures now explain refusals and tell you the reserved slug so you can retry.\n\n**What**\n\nPublishing an artifact now explains a 422 refusal directly instead of the old \"server kept reporting missing content\" loop message, a cancelled publish tells you the slug it reserved so you can retry to it, and an auto-published edit that was not approved now says so and points at the artifact owner.\n\n**Details**\n\n- The 422 message states the deploy was refused and that the re-check before re-sending also failed.\n- A new telemetry event `prepare_rerun_failed` carries `prepare_status` for that case.\n- The declined auto-publish is a distinct outcome, `auto_mode_declined`, whose text says the edit was not approved for automatic publishing and that the artifact owner can make the change from their own session.\n\n**Evidence**\n\n`prepare_rerun_failed`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}