Support Article
Performance and scalability of flow dependencies
SA-28403
Summary
When there are many cases waiting on dependencies, the user sees latencies and PEGA0001 and PEGA0042 alerts.
The alerts show most of the time elapsed being CPU time when saving a case with a dependent status.
Error Messages
Not Applicable
Steps to Reproduce
Perform any use case that uses the pxCheckFlowDependencies activity when there are many matching records for the query performed by that activity.
Root Cause
The pxCheckFlowDependencies activity fetches and evaluates all assignment dependency records for a given dependency class and status without filtering for relevancy in the query.
This is causing the PEGA0042 and PEGA0001 alerts when processing large query results. Additionally, turning on flow dependencies forces a table scan of pr_index_assignmentdeps every time a case is updated.
Resolution
The pxCheckFlowDependencies activity will be enhanced in a future release to be more efficient.
Published October 21, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.