ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Processes stuck in Aborting status for long time
Article ID: 145176
Clarity PPM SaaSClarity PPM On Premise
Processes are stuck in Aborting status for more than one day, and they never go to Aborted. BG restart does not fix the problem. What can be done?
Reset Aborting process to Aborted status
Release : All Supported Clarity releases
First, allow some time for those processes to get set to Aborted. This sometimes happens if there is a high load on BG.
If after a day or more the processes are still stuck, please use the following solution: On the database, run the query: UPDATE bpm_run_processes SET status_code = 'BPM_PIS_ABORTED' WHERE status_code ='BPM_PIS_ABORTING'
This will set all Aborting processes to Aborted. A restart is not required.
Now go ahead and run the Delete Process Instance job to clean them up.