{"version":"2.1.232","anchor":"cloud-file-sync-failures-describe-the-consequence","canonical_anchor":"cloud-file-sync-failures-describe-the-consequence","heading":"Cloud file-sync failures describe the consequence","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/cloud-file-sync-failures-describe-the-consequence","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Cloud file-sync failures describe the consequence\n\nCloud sync failures now say your session starts without untracked files instead of naming internals.\n\n**What**\n\nThe three sync-failure notices, for deadline exceeded, service unavailable and a failed file-list upload, now say the session starts without your untracked files, rather than referring to an internal git bundle.\n\n**Evidence**\n\n`Cloud file sync is unavailable for this session; starting without your untracked files`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}