{"version":"2.1.224","anchor":"remote-transcript-upload-detects-rewritten-history-and-skips","canonical_anchor":"remote-transcript-upload-detects-rewritten-history-and-skips","heading":"Remote transcript upload detects rewritten history and skips suppressed sessions","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/remote-transcript-upload-detects-rewritten-history-and-skips","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Remote transcript upload detects rewritten history and skips suppressed sessions\n\nRemote transcript uploads track message ids, so compaction no longer loses or duplicates work.\n\n**What**\n\nUploading a session transcript to the remote side no longer decides what is new by comparing a stored index against the message count, which could miss or duplicate work after a compaction. It now anchors on message ids and tracks which it has already seen, logging when it detects that history was rewritten.\n\n**Details**\n\n- Messages are counted as seen without being uploaded once the session binding has detached.\n- Uploads of compaction pairs are skipped entirely for sessions carrying history-backfill suppression, with a log line saying so.\n\n**Evidence**\n\n`[persist-remote] Skipping compact-pair upload: session carries history-backfill suppression`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}