{"version":"2.1.280","anchor":"journal-encoding-no-longer-carries-forward-usereventuuids-on","canonical_anchor":"journal-encoding-no-longer-carries-forward-usereventuuids-on","heading":"Journal encoding no longer carries forward userEventUuids on laptop side","tier":"internal","area":"Session Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/journal-encoding-no-longer-carries-forward-usereventuuids-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Journal encoding no longer carries forward userEventUuids on laptop side\n\nLaptop-side journal entries for live collaboration no longer carry forward userEventUuids\n\n**Unclear.** The finding does not say what depended on the carried-forward userEventUuids or what problem dropping them fixes.\n\n**What**\n\nThe `encodeLaptop` function, which builds a journal entry for live collaboration, used to copy over the passed-in `userEventUuids` array. It now always writes an empty array instead.\n\n**Why**\n\nThis stops old event identifiers from being carried forward into new journal entries on the laptop side of live collaboration sessions.\n\n- Area: Session Sync\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}