{"version":"2.1.283","anchor":"cloud-file-sync-now-refuses-cleanly-for-organizations-whose","canonical_anchor":"cloud-file-sync-now-refuses-cleanly-for-organizations-whose","heading":"Cloud file sync stops cleanly when an organization's compliance policy forbids it","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/cloud-file-sync-now-refuses-cleanly-for-organizations-whose","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Cloud file sync stops cleanly when an organization's compliance policy forbids it\n\nCloud file sync now recognises compliance and zero-data-retention restrictions, stops for the session and explains why instead of failing generically\n\n**What**\n\nCloud file sync (copying your project files to a cloud session) now has a dedicated way of ending when your organization's compliance policy does not allow it.\n\n- A 403 response (the server refusing access) whose resource is `compliance_restricted` or `zdr_restricted` is now treated as sync being unavailable with the cause `compliance_restricted`. Before, this case had no special handling and fell through to the generic path.\n\n- Claude Code also checks locally whether your organization has a zero-data-retention (`zdr`) or `ldr` policy.\n\n- When this happens, sync stops for the session and the session's sync is marked ended. Scheduled retries of the first-upload withdraw are no longer queued.\n\n- The status line reads that your organization's compliance policy does not allow file sync and that the cloud session keeps whatever files it already has. A running session shows \"File sync stopped for this session: your organization's compliance policy does not allow it.\" A separate notice appears when a session is created.\n\n- A new `anchor_unavailable` ending covers machines that cannot safely place the session's files into the project.\n\n**Why**\n\nPeople at organizations with compliance or zero-data-retention restrictions get a clear reason why file sync does not work, and sync stops instead of behaving as though the service were only temporarily down.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}