Universal Containers is building a Screen Flow to enhance the user experience for creating new...

A Screen element creates a transaction boundary. In the original design, the Opportunity is created before the second Screen, so that record is committed when the flow reaches the Opportunity Product Screen. If subsequent Opportunity Product creation fails, a Roll Back Records element can roll back only pending changes in the current transaction; it cannot undo the already committed Opportunity from the previous transaction. The solution is therefore to collect both sets of user input first, then create the Opportunity and Opportunity Product in the same transaction after the second Screen. A fault connector from Create Opportunity Product to Roll Back Records then cancels all pending record changes in that transaction. Salesforce explicitly documents using Roll Back Records on a Screen Flow fault path to cancel all pending changes