{"version":"2.1.246","anchor":"cloud-deletions-are-reported-as-trashed-not-erased","canonical_anchor":"cloud-deletions-are-reported-as-trashed-not-erased","heading":"Cloud deletions are reported as trashed, not erased","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/cloud-deletions-are-reported-as-trashed-not-erased","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Cloud deletions are reported as trashed, not erased\n\nFiles deleted by a cloud session are now reported as moved to trash, with paths named.\n\n**What**\n\nDeletions applied from a cloud session already went into a per-session trash folder on your machine. Now you are told, with an info line naming a few of the paths and stating plainly that the files were not erased.\n\n**Details**\n\n- The sync telemetry payload gains a `moved_to_trash` count.\n- Message wording: files were `moved to this session's trash on this machine, not erased`.\n\n**Evidence**\n\n`moved to this session's trash on this machine, not erased`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}