{"version":"2.1.277","anchor":"artifact-creation-supports-an-idempotency-key-and-reports-in","canonical_anchor":"artifact-creation-supports-an-idempotency-key-and-reports-in","heading":"Artifact creation now uses idempotency keys to avoid duplicate creates on retry","tier":"use","area":"Artifact Publish","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/artifact-creation-supports-an-idempotency-key-and-reports-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Artifact creation now uses idempotency keys to avoid duplicate creates on retry\n\nRetrying an artifact-publish or artifact-create call no longer creates a duplicate Artifact; it now reports that an earlier attempt already created it\n\n**What**\n\n- Artifact creation now computes and sends an idempotency key with the create-artifact request, guarding against duplicate creation when a call is retried.\n\n- If a create is already in progress under the same key, the server now returns a `create_in_flight` error (HTTP 409) instead of creating a duplicate; new telemetry fields `already_created` and `keyed` are logged, and responses can include `alreadyCreated: true` for replayed creates.\n\n- When an artifact-publish tool call result indicates the artifact was already created by an earlier attempt of the same call, the tool now returns \"An earlier attempt of this call already created the Artifact...\" instead of claiming a fresh creation.\n\n- Similarly, if an Artifact-from-type creation succeeds but publishing its files fails, the resulting message now checks `already_created` and, if true, reports that nothing new was created instead of always saying a new Artifact was created.\n\n**Why**\n\nThis prevents retried or duplicate artifact-creation calls, for example after a network hiccup, from producing confusing duplicate Artifacts or misleading \"Created a new Artifact\" messages.\n\n- Area: Artifact Publish\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}