---
schema_version: "1"
id: 23bc8217db7f23c5518107b6a089c0a9481e389ca330f3bb98b392e72ec05cac
title: Flow Builder Debugger Considerations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_considerations_troubleshooting.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_considerations_troubleshooting.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 46ffdee489ee4b68fdd106e2609ede2bf7cfbd8e902290027eba76c607fc0509
description: Use these considerations when you debug a flow in Flow Builder.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Flow Builder Debugger Considerations

Use these considerations when you debug a flow in Flow Builder.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.flow_ref_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Learn about the editions and user interfaces that support Flow Builder. Some Flow Builder features integrate with other Salesforce products that require additional licenses.">View supported editions.</a></td></tr></tbody></table>

![Warning](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_warning.png)

Warning When you debug a flow that contains Delete Records elements, the flow triggers the delete operation even when the flow is inactive.

## Debugging a Flow

- If you debug a flow without selecting rollback mode, the flow performs its actions, including Data Manipulation Language (DML) operations and Apex code execution. Closing or restarting a running flow doesn’t roll back actions, callouts, or changes that the flow already committed to the database.
- You can't provide values for input variables of the collection, record, or record collection type.
- Selecting **Pause** or running a Wait element closes the flow and ends debugging.
- When you debug a flow as another user, the flow makes record changes and runs actions as that user. The user’s profile and permission sets determine the flow’s object permissions and field-level access. Flows that always run in system context ignore the user’s object permissions and field-level access.
- When you select **Finish** in a flow, the debug details incorrectly show "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. Debugging tests only what’s within the flow. Other triggered flows and processes can cause a flow to run as intended during debugging but not at run time. To see how a record-triggered flow behaves in a real-world scenario, run the flow outside of debug in a sandbox and use debug logs to troubleshoot issues.
- When you debug a segment flow that contains Create Records, Update Records, or Delete Records elements, select **Run automation in rollback mode**. Select rollback mode when the flow contains invocable actions other than messaging actions, such as actions that send email, SMS, or WhatsApp messages. If you clear rollback mode, Flow Builder can't debug the flow. It shows an error that the flow contains elements that debugging doesn't support. For more information, see [Segment Flows](https://help.salesforce.com/s/articleView?id=platform.automate_flow_concepts_trigger_segment.htm&release=264.0.0&type=5 "A segment flow sends messages to people in a segment at a scheduled time. When you activate the flow, it sends messages to everyone in the segment at that time.").
- If a new flow transaction starts while a screen action’s autolaunched flow is running, the autolaunched flow fails.
- When debugging record-triggered flows, the Record Detail component determines which fields are editable.