Transcripts can mark that earlier history was withheld, usually after an account switch, and won't sync it.
What's wrong with this entry?
A 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.
- 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.
- Session state gained matching flags, surfaced to forks so a branched conversation inherits the suppression.
[persistence-sync] Refusing backfill: conversation carries a history-suppression taint, [persist-remote] Skipping compact-pair upload: conversation carries a history-suppression taint
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.