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 scenario is a flow error (also known as a flow problem execution) and can arise from many different sources. If you can fix the error through a change in the flow Rule, by modifying a Rule or creating a new Rule, the processing can resume.

In the header of Dev Studio, click Configure > Case Management > Processes > Flow Errors to access the flow errors in your current application. Your organization can copy and override the FlowProblems flow and the ToProblemFlowOperator routing activity to meet your needs.

The non-final getFlowProblemOperator activity determines the operator to inform and Assignment type. 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.

Use the following features to fix problem flows:

• Use Resume Flow if you want to resume the run of the flow that begins at the Step after the paused Step. Use 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 it. The flow uses the already-determined Decision result to select the appropriate connector and advance to the appropriate shape.
• Use Retry Last Step to resume the run of the flow by running the Step that paused. Use this option to resume flow execution that pauses due to a transient issue 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.
• 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.
• Use Delete Orphan Assignments to delete assignments for which the system cannot find the work item. Use 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: