Test or Troubleshoot Flows With the Flow Builder Debugger

If you’re testing your flow to make sure it works as expected or troubleshooting a flow that failed, the debug option in Flow Builder can be your best friend. Review step-by-step details of how your flow runs and the path the flow takes.

Required Editions

View supported editions.

User Permissions Needed
To debug a flow in Flow Builder:	View All Data
To open, edit, create, activate or deactivate a flow using all flow types, elements, and features available in Flow Builder, including Einstein and Agentforce for Flow:	Manage Flow

Warning If you debug a flow without choosing to run the flow in rollback mode, the flow performs its actions, including any DML operations and Apex code execution. Remember, closing or restarting a running flow doesn’t roll back its previously executed actions, callouts, and changes committed to the database.

This video explains the advantages of the Debug feature in Flow Builder along with tips on getting the most from the feature in your own org.

View this video in a separate tab.

The Flow Builder debug option has some limitations. See Flow Builder Debugger Considerations.

Open the flow in Flow Builder.
Click Debug.
Set the debug options and input variables.
The debug options vary depending on the flow type.
To debug the flow as another user, enable debugging as another user.
1. From Setup, in the Quick Find box, enter Process, and then click Process Automation Settings.
2. Enable Let admins debug flows as other users.
3. Save your work.
  
  Warning When you debug a flow as another user, the flow’s record changes and actions are performed as that user. Also, the user’s profile and permission sets determine the object permissions and field-level access of the flow. However, flows that always run in system context ignore the user’s object permissions and field-level access.
4. In Debug Options, select Run flow as another user and search for the user that you want to debug.
  You can debug a flow as another user only in a sandbox environment.
Click Run.
The debug details for the run appear in a panel on the right. The debug run is organized into cards (1) that highlight all of the most important information about the run. To resize the debug panel, drag the edge of the panel to your desired width, or click and (2). To search the debug run results, enter a search term in the search box (3). To copy the debug log onto your clipboard, click (4).
If you selected Debug wait element behavior when you set the debug options, select a Wait Path, and then click Continue the Debug Run for each Wait element in the flow.
The debug details for the run appear in a panel on the right.
(Optional) To restart the flow by using the same or different values for the input variables, click Debug Again.
(Optional) To convert the debug run to a test in a record-triggered flow only, click Convert to Test.