{"version":"2.1.274","anchor":"artifact-create-from-type-server-can-reject-a-client-suppli","canonical_anchor":"artifact-create-from-type-server-can-reject-a-client-suppli","heading":"Artifact create-from-type: server can reject a client-supplied request_id and get a retry without it","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-create-from-type-server-can-reject-a-client-suppli","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact create-from-type: server can reject a client-supplied request_id and get a retry without it\n\nArtifact creation retries automatically if the server rejects its request_id\n\n**What**\n\nWhen Claude Code creates an artifact from a type, it now attaches a `request_id` to the create request. If the server responds with a 400 error specifically rejecting that `request_id` field, Claude Code strips it and retries the creation once automatically, logging a `request_id_rejected` telemetry event. The result of a successful create can also now include a `provisioned` object.\n\n**Why**\n\nThis means an artifact creation that would otherwise fail outright because of a rejected `request_id` now has a chance to succeed on retry, without the user seeing an error.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}