If a flow encounters an error condition that prevents it from continuing, what happens
-
An exception is placed in the log4j file
-
The current flow is suspended and the FlowProblems flow is started
-
An email is sent to the user’s manager
-
The work object is closed
When a flow encounters an error that prevents continuation, Pega suspends the current flow and automatically starts the FlowProblems flow. This is a built-in error handling mechanism that allows the system to capture and manage flow exceptions gracefully. Option A is incorrect because while logging may occur, placing an exception in log4j is not the primary error handling behavior. Options C and D describe actions that are not the standard Pega flow error response.
When a Pega flow hits an error it can't recover from, the engine suspends the current flow execution and automatically kicks off the built-in FlowProblems flow so the issue can be surfaced and handled (e.g., routed to an admin worklist). It doesn't just silently log to a file, notify a manager by email, or simply close the work object — those aren't the platform's built-in error-handling behavior.