{"version":"2.1.281","anchor":"file-sync-apply-down-files-held-open-are-deferred-and-new","canonical_anchor":"file-sync-apply-down-files-held-open-are-deferred-and-new","heading":"File sync apply-down: files held open are deferred, and new staleBasis, deferred and heldOnly outcomes","tier":"notice","area":"Cloud Sync","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/file-sync-apply-down-files-held-open-are-deferred-and-new","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### File sync apply-down: files held open are deferred, and new staleBasis, deferred and heldOnly outcomes\n\nFile sync no longer deletes or replaces files you have open; it waits and retries them later\n\n**What**\n\nFile sync brings file changes made on the cloud side down into your local copy of the project. It now leaves files that are open on your machine alone. Instead of deleting or replacing them, it notes them and tries again in a later round.\n\nEach sync round now also reports:\n\n- `staleBasis`: files skipped because your local copy was not the version the change was based on\n\n- `deferred`: files put off because the round hit its limit on files, size or reads\n\n- `heldOnly`: true when open files were the only reason the round stopped short\n\nA file refused because of its name is now reported as `name_refused` rather than `writer_refused`.\n\n**Why**\n\nA file you are working in will not be swapped out from under you during sync. The new fields also make it clearer why a file has not come down yet.\n\n- Area: Cloud Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}