{"version":"2.1.248","anchor":"transcript-writing-stops-after-a-fatal-write-error-instead-o","canonical_anchor":"transcript-writing-stops-after-a-fatal-write-error-instead-o","heading":"Transcript writing stops after a fatal write error instead of retrying","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/transcript-writing-stops-after-a-fatal-write-error-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Transcript writing stops after a fatal write error instead of retrying\n\nA fatal transcript write error now stops writing instead of silently carrying on.\n\n**What**\n\nThe transcript writer now latches a fatal write failure. Once latched, further appends throw that error straight back, the queue drain rethrows it on the next flush rather than quietly resolving all waiters, and the local garbage-collection and compaction backstop is skipped. Previously a failed drain only logged and carried on. The latch clears when flush state is reset.\n\n**Details**\n\n- Effect for a session that hits a fatal storage condition: it stops appending rather than writing more on top of a broken file.\n\n**Evidence**\n\n`Transcript write failed (`, `storeFence`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}