Purge "RUN EXPLORER' List
It's possible to Purge/Clear the list of execution on "RUN EXPLORER" in Run Management ?
It is possible.
In general you should follow the high level purging procedures here: https://docs.software.hpe.com/OO/10.80/Content/Adminster/Administer/Data_cleanup.htm? thus rely on the flows that were constructed for purging
The flows rely on the Central API - which supports the purging of summary - check here: https://docs.software.hpe.com/OO/10.80/Content/Develop/Working_with_API/Purge_Execution_Step_Data.htm?
For the Purging execution summary flow I suggest reading its description. It is mentioned there how the inputs need to be provided to achieve your desired state
1. If deleteRunInputs, deleteRunOutputs, deleteStepLogs inputs are all "false" and purgeStatuses is left empty then running the flow will purge all data for executions (including execution summaries).
I follow steps using Flow "Purge Debug Events" from HPE Solution Content Pack, but the list of RUNS continue in RUN EXPLORER page, including the last run purge flow..
I like to clean up the list of runs on the Non-Production Environment because have a lot "garbage", many flow cancelled, with error status etc...
What version of the hpe solutions content pack are you using? There is a bug in some versions of the hpe solutions content pack where the maxAmount parameter would mean to delete only that many records instead of looping to delete all records older than x days in batches of maxAmount's value. If possible upgrade to the latest version of the hpe solutions content pack and try again.
Could you also provide the following information: what db type are you using for OO, what is the result of the purge executions step of the latest purge execution summary flow execution and what other parameters are you using, namely the value of last x days and if you are utilizing the statuses input.
Consider Vlad's mentions but keep in mind that in order to purge the summary you need to run the purge execution summary flow. the purge debug events does not handle the entire summaries as it is focused on specific debug related events.
thus run the events and run the purge execution summary.
watch Vlad here talking about purging, if needed.
Hope it helps