How can you configure a flow to resume from the point of failure after an...

Comprehensive and Detailed Explanation From Exact Extract:

Pega’s flow processing capabilities, as detailed in Pega Academy’sCase Design Missionand thePega Certified Lead System Architect Study Guide, include mechanisms to handle errors and resume flows from the point of failure. The Ticket shape is specifically designed to mark points in a flow where processing can jump or resume, such as after resolving an error.

Option A (Incorrect): There is no “Resume flow” option in the Actions menu for flows in Pega. The Actions menu typically includes options like “Add Work” or “Change Stage,” but resuming a flow requires a configured flow construct, as per theFlow Processingmodule.

Option B (Correct): The Ticket shape allows a flow to jump to a specific point when triggered, such as after an error is resolved. The pyRestartFlow ticket is a standard Pega ticket used to resume a flow from the point of failure. This is documented in theTicket Shapesection of Pega Community, which explains how tickets manage flow control.

Option C (Incorrect): The Subprocess shape is used to call another flow as a subprocess, not to resume a flow from a failure point. Calling pyRestartFlow as a subprocess is not a standard mechanism for resuming flows, per theCase Designguidelines.

Option D (Incorrect): The Assignment shape does not have a “Resume” type. Assignments manage user tasks, and while they can include error-handling SLAs, they do not directly control flow resumption, as noted in theFlow Processingmodule.