{"version":"2.1.293","anchor":"purge-command-reports-delete-failures-and-stops-cleanly","canonical_anchor":"purge-command-reports-delete-failures-and-stops-cleanly","heading":"The purge command now explains failed deletions and interrupted runs","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/purge-command-reports-delete-failures-and-stops-cleanly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### The purge command now explains failed deletions and interrupted runs\n\nWhen purge cannot delete something it now records why and says the rest is still on disk; an interrupted purge says it stopped and suggests `--dry-run`\n\n**What**\n\nThe purge command deletes stored files. When it could not delete something, it used to say only how many items failed. It now catches each failed deletion, records the reason, and adds: \"What could not be deleted is still on disk: fix the cause and run the command again, or delete those paths by hand.\"\n\nIf a purge is interrupted, it now prints \"Purge stopped before it finished\" and suggests running it with `--dry-run`, which shows what would be deleted without deleting anything.\n\n**Why**\n\nA purge that fails part way is now visible and easy to recover from, rather than leaving you unsure what was removed.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}