{"version":"2.1.239","anchor":"cloud-session-sync-says-why-files-could-not-be-written-back","canonical_anchor":"cloud-session-sync-says-why-files-could-not-be-written-back","heading":"Cloud session sync says why files could not be written back","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/cloud-session-sync-says-why-files-could-not-be-written-back","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Cloud session sync says why files could not be written back\n\nCloud sync now groups failed file writes by cause and names the paths.\n\n**What**\n\nThe pull summary now splits failures by cause instead of listing them together, naming up to a few paths in each group and noting that sync retries every turn.\n\n**Details**\n\n- Three groups: a name that collides with an existing file differing only in letter case, files with credential-like names that are never written locally, and everything else.\n- A separate line covers paths git holds behind a filter such as LFS or git-crypt, which only a commit can carry across.\n\n**Evidence**\n\n`from a file already here only in letter case`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}