{"version":"2.1.246","anchor":"sync-journal-accepts-transports-it-does-not-recognise","canonical_anchor":"sync-journal-accepts-transports-it-does-not-recognise","heading":"Sync journal accepts transports it does not recognise","tier":"internal","area":"Cloud Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/sync-journal-accepts-transports-it-does-not-recognise","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Sync journal accepts transports it does not recognise\n\nSync records survive an unfamiliar transport name instead of being thrown out entirely.\n\n**What**\n\nThe field naming how a bundle travelled changed from a fixed choice of two values to any short string, normalised to \"row\", \"direct\" or \"unknown\", with size caps looked up per transport. A newer server transport now passes through an older reader instead of invalidating the whole record.\n\n**Details**\n\n- The laptop side refuses to write a journal note whose bundle normalised to \"unknown\".\n- The same note gained an origin field that only survives the round trip as \"folder\".\n\n**Evidence**\n\n`sync journal note is not one its reader would accept, or rides with rows`\n\n- Area: Cloud Sync\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}