You are creating a Power Automate cloud flow. The cloud flow will create several SharePoint Online list items based on a variety of conditions. If any of the dependent SharePoint Online actions…

A scope action groups related SharePoint actions together so the entire group is treated as a single unit; if any action within the scope fails, the scope itself is marked as failed, enabling downstream revert logic to trigger cleanly.

Setting 'Run After' to 'Has failed' on the revert or delete actions ensures they only execute when the preceding scope has failed, implementing a compensating transaction pattern to undo partially completed changes.

The 'Perform a changeset request' action is an OData batch HTTP action used for transactional HTTP requests against external APIs, not a native SharePoint rollback mechanism within Power Automate flow logic.

Retriggering the flow run restarts the entire automation from the beginning rather than reverting specific changes already made, which would likely duplicate or compound the problem.