Processes stuck / hung - troubleshooting


Article ID: 129918


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


This document provides some tips on troubleshooting process stuck/hung issues as well as links to KBs on known causes.


Release: All Supported Releases
Component: Clarity Process Management


Tips for optimizing performance health of processes

  1. Delete old processes in the Done or Aborted state.
  2. Retry or Abort and Delete old processes in the Error state. See more details at How can I keep my process engine healthy?
  3. If the issue is related to a single process which performs some type of data load, it might be slow because of multiple instances of the process running at the same time. In this scenario checking the "Do not start a new process if one is already running" flag on process definition will help.

Log troubleshooting

Review of the bg-ca.logs / bg-system.logs can assist in determining a root cause / fix. Additionally, enabling process debugging (see KB :Process debugging - Enabling for Troubleshooting) may help further in troubleshooting.

If an error is found in the logs, searching our knowledgebase on that error may help in determining the root cause / fix needed.


Related KBs on process stuck issues

If Broadcom support assistance is needed

The below details that can aid support in troubleshooting stuck process issues:

  1. Is it just certain processes that are stuck?
  2. Do out of the box processes run okay? 
    Tip: You can check Administration-Processes->Initiated, and filter on Status of Error in case the processes are erroring versus stuck.
    • If you click on the icon on the Messages column, it will give more details of the error, and sometimes give you the ability to correct the issue from there. (Example, if there's no one to assign an action item to in the process, it gives a reassign link).
    • Some objects give specific details as to where the issue is located, example Timesheets.
  3. Do jobs appear to be running okay? 
  4. If On Premise, please provide a copy of the bg-ca.logs and bg-system.logs for the time frame the issue occurred. Enabling process debugging (see KB :Process debugging - Enabling for Troubleshooting) may help in further investigation
  5. Screen shots of the 2 below pages: 
    • Administration->Data Administration->Process Engine page. On Premise customers can also run the following query and send the results: 
select * from BPM_RUN_PROCESS_ENGINES order by heart_beat desc
    • From the Process Engine Page, click on the link to the process engine and take a screen shot of that page as well