{"version":"2.1.234","anchor":"artifact-read-back-and-database-writes-report-unknown-outcom","canonical_anchor":"artifact-read-back-and-database-writes-report-unknown-outcom","heading":"Artifact read-back and database writes report unknown outcomes instead of failures","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/artifact-read-back-and-database-writes-report-unknown-outcom","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Artifact read-back and database writes report unknown outcomes instead of failures\n\nA failed artifact request inside the cloud relay now reports an unknown outcome so Claude re-reads before retrying.\n\n**What**\n\nWhen a request to the artifact service fails inside the cloud relay, Claude is now told the outcome is unknown and to re-read before retrying, rather than being told the operation failed. That stops it repeating a write that may already have applied.\n\n**Details**\n\n- Failures on the relay path are reported as `relay_request_error` instead of `request_error`.\n- Retry-after handling now applies only to a genuine 429 from the artifact service, not to a relay response.\n- The read-back and publish calls dropped their per-call host, auth and status-validation options.\n- New telemetry for repairing nested HTML: `nested_repair_depth_cap` and `nested_repair_miss`.\n\n**Evidence**\n\n`db write outcome unknown (relay request failed) \u2014 it may have applied; read back before retrying`, `read-back relay HTTP `\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}