In Flow Builder, the Run and Debug buttons allow admins to test flows, but with key differences.

The Run button executes the flow in its current version and provides no visibility into how each element behaves.

The Debug button, however, allows the admin to enter input variables, simulate flow execution, and see detailed step-by-step outcomes such as:

Element execution paths

Variable assignments

Errors

Screens encountered

Therefore, the Debug button is best for troubleshooting and understanding flow logic in real time.

Option D is correct — it accurately reflects the purpose of the Debug button.

Incorrect Options:

A. Debug does not create a draft version.

B and C. These options are technically incorrect and unrelated to the functional difference between the buttons.

Reference Extracts from Salesforce Process Automation Study Guide:

“Use the Debug button to test flows and view real-time, step-by-step execution details including input/output values.”

“The Run button simply launches the current saved flow and does not provide logs or trace information.”

=========================================================