{"version":"2.1.281","anchor":"cloud-file-sync-gets-new-user-facing-failure-messages","canonical_anchor":"cloud-file-sync-gets-new-user-facing-failure-messages","heading":"Cloud file-sync gets new user-facing failure messages","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/cloud-file-sync-gets-new-user-facing-failure-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Cloud file-sync gets new user-facing failure messages\n\nCloud file sync gains new error messages explaining why syncing or safe file placement is not working on this machine\n\n**Unclear.** The finding does not say where in Claude Code these messages appear or what \"safe file placement\" does.\n\n**What**\n\nCloud file sync has new messages that explain what went wrong. They cover:\n\n- Safe file placement being unavailable, with reasons such as `no_ffi`, `remote_volume`, `no_procfs`, or an old macOS version.\n\n- A lock folder that cannot be used.\n\n- Cloud uploads that this machine refuses.\n\n- Sync being turned off for the rest of the session. A session is one continuous Claude Code conversation.\n\nOne of the new lines begins \"Cloud changes are not reaching this machine:\".\n\n**Why**\n\nWhen sync fails, you get a stated reason in place of silence. That gives you a starting point for fixing the problem.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}