{"version":"2.1.247","anchor":"individual-transcript-records-can-be-removed-from-a-session-","canonical_anchor":"individual-transcript-records-can-be-removed-from-a-session-","heading":"Individual transcript records can be removed from a session stream","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/individual-transcript-records-can-be-removed-from-a-session-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Individual transcript records can be removed from a session stream\n\nCode exists to delete one record from a stored session by rewriting the stream.\n\n**What**\n\nNew code can delete a single record from a stored session by rewriting the stream in place, which is the machinery a targeted deletion would need.\n\n**Details**\n\n- It walks records backwards looking for the target id in the raw bytes, then parses to confirm before rewriting.\n- The rewrite is done in place with a precondition on the current version, retried up to three times if the stream changed underneath it.\n- It stops and reports rather than looping if the stream exceeds a read budget or the backward cursor fails to move.\n\n**Evidence**\n\n`Tombstone removal abandoned: the backward record cursor did not advance`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}