{"version":"2.1.248","anchor":"file-sync-and-socket-outcome-names-reshuffled","canonical_anchor":"file-sync-and-socket-outcome-names-reshuffled","heading":"File-sync and socket outcome names reshuffled","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/file-sync-and-socket-outcome-names-reshuffled","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### File-sync and socket outcome names reshuffled\n\nFile-sync outcome messages gained new cases and dropped one blocking reason.\n\n**What**\n\nThe code that turns a setup outcome into a message gains cases for `momentary` and `too_many_paths`, gives the new unmapped-uid socket failure its own renderer, and drops `too_many_untracked` from the set of reasons that block sync, which still contains `untracked_too_large`.\n\n**Details**\n\n- The new cases have no visible message strings in this build, so what they render is not settled here.\n\n**Evidence**\n\n`\"untracked_too_large\"`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}