{"version":"2.1.232","anchor":"file-sync-reports-two-new-reasons-for-switching-itself-off","canonical_anchor":"file-sync-reports-two-new-reasons-for-switching-itself-off","heading":"File sync reports two new reasons for switching itself off","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/file-sync-reports-two-new-reasons-for-switching-itself-off","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### File sync reports two new reasons for switching itself off\n\nPer-turn file sync now explains two more reasons it switched itself off mid-session.\n\n**What**\n\nPer-turn file sync, which keeps a cloud session's files in step as a turn runs, previously only turned itself off for having too many files. It now also turns off when it cannot list the repository tree, and when the tree it cloned exceeds what per-turn sync can track, each with its own explanation naming the cloud session's originating commit or cloned repository.\n\n**Details**\n\n- The two new reasons are recorded as `tree_unlistable` and `tree_too_many_files`, joining the existing too-many-files abort in a shared set of shutoff reasons.\n- Each reason carries its own user-facing sentence rather than a generic failure.\n\n**Evidence**\n\n`File sync is off for this session: the repository the cloud session cloned has more files than per-turn sync can track`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}