Rules of Execution History Cleanup

Whoever runs the execution history cleanup must have the Clean Execution History permission through their role. This includes the following product areas:

  • Web UI: to run the Execution History Cleanup action
  • Applications: to select specific applications in the Execution History Cleanup wizard
  • Environments: to clean up process requests for specific environments

Note: The Execution History Cleanup action is available by default only for the root administrative user defined in your installation.

An execution history cleanup request will not delete any history in the following situations:

  • A process request that is not started yet
  • A process request that is currently running
  • A process request that is waiting for approval
  • An application process request that has at least one component process request that is part of the resource inventory
  • A standalone component process request that is part of the resource inventory
  • An application process request that is part of the latest desired inventory

A cleanup request is initiated for each process request to be cleaned up. If a cleanup request cannot be completed for any reason, the data is rolled back to its original state for just that one cleanup request. For each process request that is eligible to be deleted, the following information is deleted:

  • Logs
  • Attachments
  • Approvals
  • Workflow traces
  • Tasks
  • Basic process requests
  • Deployment process requests for application process requests (not deleted if the deployment process request has more than one application process request)
  • Pipeline execution requests
  • Process request property contexts
  • Process request property sheets