{"version":"2.1.321","anchor":"artifact-db-new-store-read-only-error","canonical_anchor":"artifact-db-new-store-read-only-error","heading":"Writes to a read-only artifact now come back with a clear reason","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/artifact-db-new-store-read-only-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Writes to a read-only artifact now come back with a clear reason\n\nRefused writes to the artifact database can now report that the document is read-only, and that nothing in a refused batch was written\n\n**What**\n\nWrites to the artifact database can now fail with a `store_read_only` error. The message says the document is read-only, including documents that are page-only. When the write was part of a batch, the message says the batch is all-or-nothing and nothing was written.\n\n**Why**\n\nClaude gets a clear reason when an artifact write is refused, rather than a vague failure. This only happens when the server returns that error.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}