{"version":"2.1.247","anchor":"deleting-a-transcript-message-falls-back-to-a-streaming-scan","canonical_anchor":"deleting-a-transcript-message-falls-back-to-a-streaming-scan","heading":"Deleting a transcript message falls back to a streaming scan instead of giving up","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/deleting-a-transcript-message-falls-back-to-a-streaming-scan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Deleting a transcript message falls back to a streaming scan instead of giving up\n\nDeleting a transcript message now retries with a backwards scan instead of giving up.\n\n**What**\n\nRemoving a message from a transcript stored in the newer on-disk format used to abandon the deletion when reading the end of the file failed. It now retries with a record-by-record scan that pages backwards through the file.\n\n**Details**\n\n- The fallback only runs when the read error matches a specific recoverable case; other errors still abandon as before.\n- The scan is bounded by a sliding window size, a page size and a maximum number of bytes read.\n- It logs its own failure, `Tombstone removal abandoned: stream stat failed`, when it cannot even size the file.\n\n**Evidence**\n\n`Tombstone removal abandoned: stream stat failed`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}