nerdexam
Salesforce

PDI · Question #186

What are two considerations for running a flow in debug mode? Choose 2 answers

The correct answer is B. Clicking Pause or executing a Pause element closes the flow and ends debugging. C. Input variables of type record cannot be passed into the flow. When debugging a flow, the debug session ends if a Pause element is encountered or clicked, and it's not possible to pass input variables of the Record type directly into the flow.

Submitted by haruto_sh· Apr 18, 2026Testing, Debugging, and Deployment

Question

What are two considerations for running a flow in debug mode? Choose 2 answers

Options

  • ACallouts to external systems are not executed when debugging a flow.
  • BClicking Pause or executing a Pause element closes the flow and ends debugging.
  • CInput variables of type record cannot be passed into the flow,
  • DDML operations will be rolled back when the debugging ends.

How the community answered

(56 responses)
  • A
    5% (3)
  • B
    93% (52)
  • D
    2% (1)

Why each option

When debugging a flow, the debug session ends if a Pause element is encountered or clicked, and it's not possible to pass input variables of the Record type directly into the flow.

ACallouts to external systems are not executed when debugging a flow.

Callouts to external systems *are* executed during a flow debug run, meaning external integrations will be invoked and affected, contrary to the statement.

BClicking Pause or executing a Pause element closes the flow and ends debugging.Correct

During a flow debug run, if the flow encounters a Pause element or the user manually clicks 'Pause,' the debug session immediately terminates because the debugger cannot simulate a pause state effectively, requiring awareness of this limitation.

CInput variables of type record cannot be passed into the flow,Correct

Salesforce Flow Debugger currently does not support passing input variables of the 'Record' data type directly into the flow for testing; only primitive data types like Text, Number, or collections of primitives are supported.

DDML operations will be rolled back when the debugging ends.

DML operations performed within a debug flow are *always* rolled back at the end of the debug session, ensuring no permanent changes are saved to the database; this is a safety feature rather than a negative consideration for debugging.

Concept tested: Salesforce Flow debug mode characteristics

Source: https://help.salesforce.com/s/articleView?id=sf.flow_test_debug.htm&type=5

Topics

#Flow Debugging#Flow Limitations#Process Automation

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PDI Practice