{"version":"2.1.280","anchor":"artifact-database-writes-can-now-carry-a-request-id-for-safe","canonical_anchor":"artifact-database-writes-can-now-carry-a-request-id-for-safe","heading":"Artifact database writes can now carry a request_id for safer retries","tier":"internal","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/artifact-database-writes-can-now-carry-a-request-id-for-safe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Artifact database writes can now carry a request_id for safer retries\n\nArtifact database writes can now include a request_id so retries after a failure aren't duplicated\n\n**What**\n\nWhen Claude Code writes to the artifact database (both single and batch writes), it can now attach a `request_id` to the request so the server can recognize if the same request was already received, for example after a retry. If the server says it doesn't support the `request_id` field, Claude Code removes it and retries once, then remembers that refusal for a cooldown period so it doesn't keep sending a field the server will reject.\n\n**Why**\n\nThis makes retried artifact writes safer by letting the server tell duplicate requests apart from new ones, while avoiding wasted retries against servers that don't support the feature.\n\n- Area: Artifacts\n- Names: `request_id`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}