Managing problem flows on the Flow errors page
Flow errors are error conditions that a flow encounters as it runs that prevent it from continuing. For example, the flow might reference a Rule that is not found at runtime. This is called a flow error, or a flow problem execution, and can happen for many different reasons. However, if you can fix the error by making a change in the flow Rule, by modifying an existing Rule or creating a new Rule, then processing can resume.
When a flow error occurs during a case run, Pega Platform™ automatically initiates a specialized error-handling process, called a Problem Flow. This automated mechanism facilitates detection, analysis, and repair of cases in flight, without loss of processing progress. The Problem Flow system ensures consistent delivery of business outcomes when run time exceptions occur. The system invokes different Problem Flow types based on the error category, such as ConnectionProblem for integration issues, pzStageProblems for stage configuration errors, and pyRemoteProblem for remote case creation failures.
In the header of Dev Studio, click Configure > Case Management > Processes > Flow Errors to access a report on any flow errors in your current application. Your organization can copy and override the FlowProblems flow and the ToProblemFlowOperator routing activity to better meet your needs.
The non-final getFlowProblemOperator activity determines which operator to inform, and what the Assignment type should be. The default values are Broken Process and Workbasket, respectively. Each row in the report signifies an individual flow problem, which might represent a shared condition or unrelated conditions generated by many applications.
Methods of fixing problem flows
Use the following features to fix problem flows:
-
Resume Flow
Use Resume Flow to resume the flow at the step after the paused step. Select this option when the application performs a valid action that the flow does not represent. For example, a flow contains a Decision shape that evaluates a decision table. If the decision table returns a result that does not correspond to a connector in the flow, add the connector to the Decision shape and resume the flow. The flow uses the already-determined decision result to select the appropriate connector and advance to the next shape. -
Retry Last Step
Use Retry Last Step to resume the flow by running the step that paused. Select this option to resume flow runs that pause due to transient issues, such as a connector timeout or failure, or if you resolve an error by reconfiguring a Rule used by the flow. For example, if you add a missing result to a decision table to fix a flow error, select Retry Last Step to reevaluate the decision table and determine the appropriate flow connector. -
Restart Flow
Use Restart Flow to start the flow at the initial step. If an issue requires an update to a flow step that the application has already processed, resume the flow at the initial step. -
Delete Orphan Assignments
Use Delete Orphan Assignments to delete assignments for which the system cannot find the work item. Select this option to resolve flow errors caused by a user lacking access to a necessary Rule, such as an activity, because of a missing Ruleset or privilege. Selecting Delete Orphan Assignments resolves an assignment that a user is otherwise unable to perform.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
Want to help us improve this content?