Skip to main content

Archive runs and results

Running a policy​

Scheduled policies run on their cadence. To run one immediately, open the policy and click Run archive policy. Because a run ends by deleting records from Salesforce, the confirmation is explicit:

This captures the records in scope, verifies the copy is durably stored, and then permanently deletes those records from the Salesforce org. The archived copy is kept and stays restorable, but the records will no longer exist in Salesforce.

You can also Disable a policy to pause its schedule (existing runs and archived data are kept) and Enable it again later.

A run's report​

An archive run's page mirrors a backup run: live progress, stat cards, and an Archive Details table — per object: how many records were archived, how many were deleted from Salesforce, and the status.

[SCREENSHOT REQUIRED: Archive run page with per-object archived/deleted counts]

The delete report, per object​

Open an object to see its Archive delete card — the honest account of what happened after the capture was verified:

  • The number of records removed from the org, and whether that was a hard delete (storage reclaimed immediately) or a soft delete (recoverable from Salesforce's Recycle Bin for a window).
  • How many files were kept because they're still shared with records outside the archive.
  • Failed to delete (N) — records that were captured but couldn't be removed from Salesforce, each with the record Id and Salesforce's exact error, plus a Download all errors button for the full list. The archived copy is intact and the records still exist in Salesforce, so the delete can be safely retried.
  • Review relationships — out-of-scope relationships this delete touched, labeled by effect:
    • May block the delete — a restrict-delete child can refuse the parent's deletion.
    • Cascade-deleted — a master-detail child Salesforce removes with the parent (not archived!).
    • Lookup orphaned — the child stays; its link is simply cleared.

[SCREENSHOT REQUIRED: Archived object detail with the Archive delete card and failed-to-delete list]

Cleaning up leftovers​

If records repeatedly refuse deletion (blocking relationships you don't want to archive), the archived copy remains valid — you can leave them, widen the scope, or use Purge as a targeted cleanup for records whose copy is already safe in the archive.