{"version":"2.1.281","anchor":"session-transcript-write-failure-marks-the-record-lost","canonical_anchor":"session-transcript-write-failure-marks-the-record-lost","heading":"Session transcript write failure marks the record 'lost'","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/session-transcript-write-failure-marks-the-record-lost","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Session transcript write failure marks the record 'lost'\n\nWhen saving a session transcript fails, the failed record is now marked as lost\n\n**Unclear.** The finding does not say what reads the `\"lost\"` mark or what the reader sees because of it.\n\n**What**\n\nWhen saving part of a session transcript (the saved log of a conversation) fails, Claude Code now marks that record as `\"lost\"` before reporting the error as before.\n\n**Why**\n\nA failed save is now noted explicitly instead of only raising an error."}