{"version":"2.1.274","anchor":"artifact-publishversion-actions-now-thread-a-requestid-for","canonical_anchor":"artifact-publishversion-actions-now-thread-a-requestid-for","heading":"Artifact publish\/version actions now thread a requestId for idempotency","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-publishversion-actions-now-thread-a-requestid-for","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact publish\/version actions now thread a requestId for idempotency\n\nArtifact publish actions now pass a requestId through to the backend for idempotency\n\n**What**\n\nThe artifact publish \"version\" action, along with its three underlying implementations (workshop files-only publish, live-doc publish, and the general publish path), now pass a `requestId` taken from the incoming request through to the backend publish call.\n\n**Why**\n\nThreading a request ID through publish calls supports idempotency, meaning a repeated or retried publish request can be recognized as the same request rather than causing a duplicate action.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}