{"version":"2.1.221","anchor":"transcript-write-failures-only-degrade-the-session-for-the-s","canonical_anchor":"transcript-write-failures-only-degrade-the-session-for-the-s","heading":"Transcript write failures only degrade the session for the session's own files","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/transcript-write-failures-only-degrade-the-session-for-the-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Transcript write failures only degrade the session for the session's own files\n\nAn unrelated file write failure no longer degrades your session's transcript recording.\n\n**What**\n\nA write failure on an unrelated path no longer flips the transcript writer into its degraded state.\n\n**Details**\n\n- Degraded state is entered only when a session transcript path is actually armed and the failing path is not on the ignore lists.\n- Failures recorded before any path is armed are tracked separately rather than counted against the session.\n- `tengu_transcript_write_failed` and `tengu_transcript_writer_recovered` continue to fire as before.\n\n**Evidence**\n\n`tengu_transcript_write_failed`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}