{"version":"2.1.239","anchor":"directory-sync-can-now-delete-files-keeping-a-local-copy-whe","canonical_anchor":"directory-sync-can-now-delete-files-keeping-a-local-copy-whe","heading":"Directory sync can now delete files, keeping a local copy when unsure","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/directory-sync-can-now-delete-files-keeping-a-local-copy-whe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Directory sync can now delete files, keeping a local copy when unsure\n\nDirectory sync can now remove files deleted upstream, trashing them and leaving anything it is unsure about.\n\n**What**\n\nThe background worker that syncs a directory gained the ability to remove files that are gone upstream, moving them to the trash rather than deleting outright, and leaving them in place when it cannot tell whether your copy changed.\n\n**Details**\n\n- New counters report deletes considered, files trashed, copies kept because they changed or because their state was unknown, mismatched deletion records, files already absent, and trashing being unavailable, refused or failed, plus retry counts per lane.\n- Replacing a file can now stash a copy first and discard it if the rename succeeds; the result says whether an unstashed file was overwritten.\n- No flag controlling this behaviour is visible in the changed code.\n\n**Evidence**\n\n`trash_failed`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}