Clarity processes keep executing even if process got set on hold

Products

• Clarity FedRAMP
• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Due to a mistake on our side thousands of processes got initiated. These processes contain a GEL script that calls other processes. Main process got set on hold to avoid more process executions and initiated instances got removed. However, 24 hours later, there are still processes being executed. Does Clarity have any kind of temporary table that holds information about processes that are not yet executed, but need to be initiated when the process engine can handle the task?

Environment

Any supported Clarity release

Resolution

Process instances that have been already executed are stored at the BPM_RUN_PROCESSES table

All process instances that have already been **created** (statuses such as Running, Error, Aborting, etc.). There is no separate “queued” status; if they exist here, they have already been started.

Process Engine events are stored at the NMS_MESSAGES and NMS_MESSAGE_DELIVERY tables.

Process engine **events** are stored here, including **“start process”** events. Until the event is processed, no row exists in BPM_RUN_PROCESSES table.

If you face this issue, you might want to:

Look at at the NMS_MESSAGES and NMS_MESSAGE_DELIVERY tables and check what these tables hold (truncate the tables or remove the undesired entries to stop events form executing processes)

Look at the BPM_RUN_PROCESSES table to understand what processes are running (update the process status of the processes that initiated by mistake)

With any doubts contact Broadcom Support