{"version":"2.1.248","anchor":"cleared-sync-folders-get-a-file-sync-stopped-md-marker","canonical_anchor":"cleared-sync-folders-get-a-file-sync-stopped-md-marker","heading":"Cleared sync folders get a FILE_SYNC_STOPPED.md marker","tier":"notice","area":"File Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/cleared-sync-folders-get-a-file-sync-stopped-md-marker","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Cleared sync folders get a FILE_SYNC_STOPPED.md marker\n\nWhen sync clears a folder it leaves a FILE_SYNC_STOPPED.md explaining what happened.\n\n**What**\n\nWhen directory sync clears a repository folder, it moves the contents aside (`.git` first) and leaves a file called FILE_SYNC_STOPPED.md at the root explaining what happened, listing anything it could not move.\n\n**Details**\n\n- Each listed name is sanitised and truncated to 120 characters with an ellipsis.\n- Failures are recorded as telemetry: unlisted entries, rename failures and marker-write failures, plus read\/write failures for the persisted record.\n- That record tracks a phase of clearing, cleared or untouched.\n- Whether this runs at all depends on directory sync being active for your session.\n\n**Evidence**\n\n`These entries could not be moved and are still here: `\n\n- Area: File Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}