Paused and failed flow interviews
Key Takeaway
A paused interview is saved so it can continue later, and it keeps using the flow version that was active when it paused. You can see all failed and paused interviews in one place on the Monitor tab.
A flow interview is one run of a flow. An interview can pause and continue later, and it fails when it hits an error that no fault path handles. App builders need to know where to find paused and failed interviews, how to resume, debug, or delete them, and which rules can block or break them.
How an interview pauses
An interview pauses in one of two ways. A user clicks "Pause" on a flow screen, or the flow runs a Wait element and waits for a resume event. Either way, Salesforce saves the paused interview as a record so it can continue later.
Every interview, whether running or paused, has a GUID, but it gets an 18-character Salesforce ID only when it pauses and is saved as a record. You can store extra details about interviews in a custom object by referencing the interview's GUID.
Users can pause on a screen only after you turn the feature on. From Setup, open Process Automation Settings and select "Let users pause flows". This needs the Customize Application permission. Screens then show the Pause button automatically.
For example, a service rep can pause an interview when the customer doesn't have all the needed information.