{"version":"2.1.227","anchor":"transcripts-can-record-that-history-was-deliberately-withhel","canonical_anchor":"transcripts-can-record-that-history-was-deliberately-withhel","heading":"Transcripts can record that history was deliberately withheld","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/transcripts-can-record-that-history-was-deliberately-withhel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Transcripts can record that history was deliberately withheld\n\nTranscripts can mark that earlier history was withheld, usually after an account switch, and won't sync it.\n\n**What**\n\nA new transcript entry marks a session whose earlier history was suppressed, most often because the signed-in account changed. Replay skips it, and remote sync refuses to backfill or upload the merged pair produced by compaction for any conversation carrying that mark.\n\n**Details**\n\n- The record holds a session id, a cause and optionally the account it was vetoed against; duplicate detection for it uses only the type and session id.\n- Session state gained matching flags, surfaced to forks so a branched conversation inherits the suppression.\n\n**Evidence**\n\n`[persistence-sync] Refusing backfill: conversation carries a history-suppression taint`, `[persist-remote] Skipping compact-pair upload: conversation carries a history-suppression taint`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5"}