Skip to main content
Verify the version tags to ensure you are consuming the intended content or, complete the latest version.

Resolving flow issues by using problem flows 

When an operator completes an assignment, and a problem arises with the flow, the primary flow execution is paused, and a standard problem flow starts. A standard problem flow enables an administrator to determine how to resolve the flow.

Pega Platform™ provides three standard problem flows: FlowProblems for general process configuration issues, pzStageProblems for stage configuration issues, and ConnectionProblem for Integration issues. The problem flow administrator identifies and manages problem flows on the Flow Errors landing page.

Note: As a best practice, override the default workbasket or problem operator settings in the getFlowProblemOperator  activity in your application to route the problem to the appropriate destination.

Customize FlowProblems

Copy the FlowProblems flow to your application to support your requirements. Do not change the name key. In this example, you add a Send Email Smart Shape to each of the CancelAssignment actions to notify the manager when the cancellations occur.

Flow Problem
In this diagram, the FlowProblems flow has two assignments, one that routes to a work queue, the other to a worklist. Both assignments route to Param.OperatorToInform. Both assignments have four actions, CancelAssignment, RestartProblemFlow, RetryProblemStep, and RetryFromBeginning. When CancelAssignment action is submitted an email is sent to the configured receipent.

Stage-related problem flows

Problem flows can arise due to stage configuration changes, such as when a stage is removed or relocated. When an assignment is unable to process due to a stage-related issue, the system starts the standard pzStageProblems flow.

stage problems
This figure shows how the pzStageProblems flow is defined. The fork shape at the top avoids the assignment if the flow is being executed in APP Studio. Otherwise, the flow pauses at an assignment named pzStageProblems. Two actions are available, Change Stage and Cancel Assignment.

In the following example, assume the Booking stage has been refactored to be a separate case type. A Booking case creation step and a wait step were added at the end of the Request stage's process. As a result, you remove the unnecessary Booking stage within the parent stage's case life cycle. Finally, any inflight assignments that existed in the Booking stage were not moved back to the Request stage using a bulk processing activity.

Stage Problem stage

When a user attempts to advance a case formerly situated in the removed Booking stage, the pzStageProblems flow would be initiated. Within this flow, the operator can use the Actions menu to select Change stage.

Stage Problem  Change stage
In this diagram, from the case action menu user can select “Change stage “ to manually advance the case.

The operator can then manually move the case to another stage, the Request stage being the most appropriate choice.

In this diagram, the user can manually advance the case to a different stage by picking the appropriate option from the drop-down menu.

For backward compatibility, consider temporarily keeping an outdated stage and its steps as they are. For newly created cases, use a Skip stage when the condition in the Stage Configuration dialog box to bypass the outdated stage.


A flow execution can call an external system such as a relational database, Enterprise JavaBean, or Web service through an Integrator shape on a flow rule. The activity referenced in the Integrator shape references a connector rule (for example, a Connect SOAP rule) that controls the communication and data exchange with the external system.

To facilitate the detection of problems and analysis or repair such events, you can designate a flow rule for connector exceptions in your application. Failure of an Integrator shape causes the designated flow rule to start. The flow rule can send out email correspondence, attempt retries, skip over the integrated step, or send an assignment to someone.

For connectors, Pega Platform calls the ConnectionProblem flow. You can override and customize the ConnectionProblem flow to support your requirements.

Connection problem
This figure shows how ConnectionProblem is defined. The fork shape at the top avoids the assignment if the called resource is available and executes sub-flow FlowProblems. Otherwise, the flow pauses at an assignment named WaitForRetry. Two actions are available, Cancel Assignment and Resume Problem Flow.


This Topic is available in the following Module:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice