{"version":"2.1.282","anchor":"artifact-publish-an-identical-resubmission-against-a-moved","canonical_anchor":"artifact-publish-an-identical-resubmission-against-a-moved","heading":"Resending identical artifact content after the live version moved gets its own refusal","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/artifact-publish-an-identical-resubmission-against-a-moved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Resending identical artifact content after the live version moved gets its own refusal\n\nPublishing the same artifact content again after its live version has changed now fails with a dedicated reason and guidance\n\n**What**\n\nWhen Claude tries to publish an artifact with exactly the same content as before, and the artifact's live version has moved on since, publishing now fails with the reason `identical_resubmission_moved` and a message guiding what to do next. The refusal is recorded. Before, this case got the general refusal for identical resubmissions.\n\nThe other checks against publishing over an out-of-date version now also record where the attempt came from.\n\n**Why**\n\nClaude gets a clearer route to recover when it resends stale artifact content.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}