Contents
How do I debug a flow to another user?
How: In Setup, go to Process Automation Settings and select the Let admins debug flows as other users checkbox.
- Next open a flow in Flow Builder and click Debug.
- The flow debug run then starts with you as the impersonated user.
How do I debug a flow error in Salesforce?
Remember, closing or restarting a running flow doesn’t roll back its previously executed actions, callouts, and changes committed to the database.
- Open the flow in Flow Builder.
- Click Debug.
- Set the debug options and input variables.
- Click Run.
Can we debug flows in Salesforce?
Whether you’re testing a new flow or troubleshooting a flow that fails, the debug option in Flow Builder can be your best friend. See real-time details of what your flow does, easily set input variables, and restart the flow anytime to debug a different branch.
How do you skip a flow step?
When the steps that you want to skip is in the middle of the flow, you can bundle all of those steps in a Scope control. After that, set the “Configure run after” of the Scope control to “is skipped” or “has timed out” and set the step afterwards as “is skipped” too.
How can I debug a flow on my computer?
For Screen flow type, you can debug the flow in a separate window. When you click Debug on the upper right toolbar, you will see a prompt message where you can set the debug options. Run the latest version of each flow called by subflow elements: By default, the system will run the active version of your referenced flow (ex. subflow).
When to run as a specific user in debug?
When debugging a flow we get the option so add any input parameters to alter the behavior and test different outcomes based on different inputs. Sometimes permissions are the cause of an unhandled method and it would be useful to run as the specific user to see the error when debugging.
How to debug a flow and understand error messages?
For Autolaunch/Record-Triggered/Scheduled-Triggered flow type, you can debug the flow directly on the canvas. After setting the debug options, you will see the details on the canvas, how the flow is executed (Orange arrow), and where the error shows (Red stop sign).
Can you run screen flows as a specific user?
Sometimes permissions are the cause of an unhandled method and it would be useful to run as the specific user to see the error when debugging. Screen flows can now be run in the Flow debugger as another user, though with some important requirements and limitations that are documented in the release notes.