RECORD RETENTION · Workflow idea
For an administrator responsible for an automation environment, prepare a cleanup plan that retains a chosen number of recent run records per process and identifies older entries for removal. Deletion can remove evidence needed for troubleshooting, audits, or investigations, and one run may cover only a limited portion of the history. Confirm the retention policy, preserve required records and backups, preview the affected items, test recovery, and require an authorized owner to approve deletion before activating the cleanup.
01 / The starting point
An administrator-approved retention policy, defined environment scope, and recovery plan
“Reduce unnecessary history while retaining records required for operations and accountability.”
02 / The work
Helps an administrator identify older automation run records beyond a configured retention count and remove them from the selected environment.
Confirm which records may be removed and which are needed for support, audit, or investigations.
Set how many recent records to keep for each process and document the rationale.
Check how many and which statuses are in scope, and note any older records not included in the review.
Confirm the records can be restored or are no longer required before deletion.
Have an authorized administrator confirm the scope, review deletion results, and retain an audit note.
03 / The result
A reviewed cleanup plan with affected-record counts, retention settings, and deletion approval.
Reviews & approvals · Example outcome
A reviewed cleanup plan with affected-record counts, retention settings, and deletion approval.
This process deletes operational records, potentially including failed runs, and may retrieve only a limited set in each pass. Review scope and counts, preserve required audit history, test a backup and recovery path, and approve the exact deletion plan before activation.
04 / Make it yours
A few choices shape the work around your team.
Identify operational, legal, and incident records that must not be removed.
Account for per-run record limits and avoid broad deletion defaults.
Verify a recent backup can restore the records and environment needed for operations.
Keep the cleanup paused until counts, scope, and affected records have been reviewed.