Work items which are stuck in infinite loops impact Chorus BPM system performance, and in some cases system stability. This issue impacts both hosted and self-hosted clients.
When we see high CPU utilisation on the application and database servers, we query the WA2 BI event table to find work items which are stuck in a loop. This reactive step allows us to identify the work items which are impacting performance but doesn't address the root cause.
We could like Chorus BPM design studio to identify potential infinite loops as part of process validation. The beta process test automation framework was able to identify loops. Maybe this code could be used as the basis of a solution?
