You are here:
Flow Builder Debugger Considerations
Keep these considerations in mind when using the debug option in Flow Builder.
Required Editions
| View supported editions. |
Warning Be careful when debugging flows that contain delete elements. Even if the
flow is inactive, it triggers the delete operation.
Debugging a Flow
- 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.
- You can’t pass values into input variables of type collection, record, and record collection.
- Clicking Pause or executing a Wait element closes the flow and ends debugging.
- 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.
- When you click Finish in a flow, the debug details incorrectly state “Selected Navigation Button: NEXT.”
- When you debug a schedule-triggered flow, the flow starts only for one record.
- Record-triggered flows always run in rollback mode. When you debug a record-triggered flow, only what’s within the flow is tested. This smaller scope can lead to scenarios where the flow executes as intended while debugging, but not at run time. This behavior difference can be due to other triggered flows and processes. To see how a record-triggered flow behaves in a real-world scenario, you should run the flow in a sandbox org outside of debug, and instead use debug logs to troubleshoot any issues.
- When debugging a screen action in a screen flow, if a new flow transaction starts while the screen action’s autolaunched flow is running, the autolaunched flow fails
- When debugging record-triggered flows, editable fields are based on the fields available in the Record Detail component.
Did this article solve your issue?
Let us know so we can improve!
