{"version":"2.1.242","anchor":"transcript-storage-failures-now-say-which-system-error-cause","canonical_anchor":"transcript-storage-failures-now-say-which-system-error-cause","heading":"Transcript storage failures now say which system error caused them","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/transcript-storage-failures-now-say-which-system-error-cause","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Transcript storage failures now say which system error caused them\n\nTranscript save errors now name the underlying system error, so a failed write says why.\n\n**What**\n\nErrors saving transcripts carry the underlying operating-system error code and a telemetry code in their message, so a failed append, move or folder creation identifies its cause.\n\n**Details**\n\n- A folder-creation variant was added alongside the existing append and move errors.\n- A check that withholds an append when the target file is missing now reports \"onlyIfExists stat failed (\u2026) \u2014 append withheld\".\n\n**Evidence**\n\n`transcript storage folder creation failed`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}