An administrator selects all snapshots greater than 14 days in Reclaim Capacity and creates a...

The scheduled Reclaim action is created from the snapshot candidates visible at scheduling time, but execution still depends on the valid runtime state of each selected object. VCF Operations Reclaim supports scheduling snapshot reclamation from the Reclaim page; the administrator expands the cluster, selects one or more VMs or snapshots, and uses Schedule Action to run deletion later, with the job managed in Automation Central . The underlying delete snapshot action first retrieves snapshots based on age, then deletes selected snapshots, and the resulting task status is tracked in Recent Tasks . If a user reverts a VM to one of those snapshots before the scheduled job runs, that snapshot becomes part of the VM’s active rollback/current-state chain rather than an unused candidate that should be safely reclaimed. vSphere snapshot behavior requires caution because deleting a snapshot removes the ability to return to that snapshot state, and reverting changes the VM’s active snapshot relationship . Therefore, the reverted snapshot is not deleted, while the rest of the scheduled snapshot deletions can continue. The overall job is expected to finish as partially successful , reflecting that some selected objects were processed while the reverted snapshot was skipped or failed validation. Reference topic: Objective 4.2 – Reclaim Capacity / Snapshot Reclamation / Scheduled Actions / Automation Central .