{"version":"2.1.229","anchor":"transcript-writes-can-be-routed-through-a-storage-backend","canonical_anchor":"transcript-writes-can-be-routed-through-a-storage-backend","heading":"Transcript writes can be routed through a storage backend","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/transcript-writes-can-be-routed-through-a-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Transcript writes can be routed through a storage backend\n\nTranscript writes can go through a storage backend instead of plain files, but files remain the default.\n\n**What**\n\nTranscript appends, hydration, forking, snapshot copies, job timelines and history-suppression records all accept an optional storage backend and key. When one is supplied, writes go through that backend; with none supplied they fall back to a plain file append, which is what happens by default. Backend failures are re-shaped into standard errno-style errors so they show up in telemetry the same way file errors do.\n\n**Details**\n\n- Failure log line: `transcript storage append failed`\n- Backend path uses append, replaceRecords and stat operations\n\n**Evidence**\n\n`transcript storage append failed`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}