Loading
Automate Your Business Processes
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Debug an Orchestration Without Changing Your Data

            You are here:

            1. Salesforce Help
            2. Docs
            3. Automate Your Business Processes

            Debug an Orchestration Without Changing Your Data

            Debug your orchestration in Flow Builder to ensure that it runs as expected or to determine the cause of unexpected errors. Use rollback mode to debug your orchestration without making changes to your Salesforce data.

            Required Editions

            View supported editions for Flow Orchestration.
            User Permissions Needed
            To debug an orchestration Manage Flow

            Open the Orchestration from the Automation App

            Open an orchestration from the Orchestration page in the Automation Lightning app.

            1. On the navigation bar, click App Launcher icon.
            2. In the search box, enter automation, and then select Automation.
              The Automation app opens.
            3. In the Automation app, select the Orchestrations tab.
              The Orchestrations list view opens.
            4. Click the label of the orchestration, and then click View in Flow Builder.
              The orchestration opens in Flow Builder.

            Open the Orchestration from Setup

            In Setup, open an orchestration from the Flows list view.

            1. Click Gear icon, and then select Setup.
            2. From Setup, in the Quick Find box, enter Flows, and then select Flows.
            3. Click the label of the orchestration.
              The orchestration opens in Flow Builder.

            Manage Start Points and End Points

            Set a start point to skip earlier stages, an end point to stop before later stages, or both to isolate a middle segment. Set start points and end points only on Stage elements. To test a single stage, set it as both the start point and the end point. Steps in skipped stages don’t produce output values, even when they have configured test output, so configure test input for steps that rely on their output. Use multiple end points when testing decision paths. Start and end points aren’t saved when you save the orchestration.

            Saving an orchestration also saves mock input. Clicking Reset Debug Settings doesn't affect mock input.

            1. (Optional) Set a start point and configure test input for the synchronous background steps that rely on output from stages that didn’t run.
              1. Hover over a stage.
              2. Click The actions icon.
              3. Select Select as Start Point.
                The
                start point icon
                appears on the stage element.
              4. Select a synchronous background step that relies on output from a stage that didn’t run.
              5. In the Step panel’s Configure Test Input tab, enter the necessary values for the step.
                When you enter a test value, its toggle is set to Included.
              6. To configure test input for additional steps that rely on output from stages that didn't run, repeat steps 1d and 1e.
            2. (Optional) Remove a start point and ignore test input for synchronous background steps.
              1. Hover over a stage.
              2. Click The actions icon.
              3. Select Selected as Start Point.
              4. Select a synchronous background step with configured test input.
              5. In the Step panel's Configure Test Input tab, set the toggle to Not Included for the input values you want to ignore.
              6. To ignore configured test input values for additional synchronous background steps, repeat steps 2d and 2e.
            3. (Optional) Set an end point.
              1. Hover over a stage.
              2. Click The actions icon.
              3. Select Select as End Point.
              The
              end point icon
              appears on the stage element.
            4. (Optional) Remove an end point.
              1. Hover over a stage.
              2. Click The actions icon.
              3. Select Selected as End Point.

            Configure the Triggering Record for a Record-Triggered Orchestration

            To debug a record-triggered orchestration, set the triggering record. This setting persists for the current Flow Builder session. Trigger a record-triggered orchestration in one of three ways: only when a record is created, only when a record is changed, or when a record is either created or updated.

            Flow Builder preserves the selected triggering record value and setup option when you switch between Edit mode and Debug mode. Refreshing your browser or closing Flow Builder clears these selections.

            1. On the Button Bar, click Debug.
              The Debug panel opens with the Setup tab selected.
            2. For an orchestration that’s triggered when a record is either created or updated, select the type of trigger to debug for.
              • To debug a trigger on a new record, for Run the automation As If The Record Is, select Created.
              • To debug a trigger on a record change, for Run the automation As If The Record Is, select Updated.
            3. In the text box, select the record to use for the debug run’s triggering record.
            4. Select Run automation in rollback mode.
            5. To manually clear debug settings, click Reset Debug Settings.

            Set Input Variables for an Autolaunched Orchestration

            To debug an autolaunched orchestration, set values for all of its input variables. The debug run fails if any input variable is missing or invalid. The values you specify persist for the current Flow Builder session.

            Flow Builder preserves the input variable values and setup option when you switch between Edit mode and Debug mode. Refreshing your browser or closing Flow Builder clears these debug settings.

            1. On the Button Bar, click Debug.
              The Debug panel opens with the Setup tab selected.
            2. On the Setup tab, enter values for each relevant input variable.
            3. Select Run automation in rollback mode.
            4. To manually clear debug settings, click Reset Debug Settings.

            Set Mock Output for Steps

            Set mock output for all asynchronous steps. For synchronous steps, defining mock output is optional. A step configured to use mock output, doesn’t run its referenced flow.

            Orchestration runs process a background step asynchronously when the step’s underlying flow contains 1 or more Action, Subflow, or Wait elements. Orchestration runs process all interactive steps asynchronously.

            Saving a flow approval process also saves mock output. Clicking Reset Debug Settings doesn't affect mock output.

            1. In the Debug panel, click the Stages tab.
            2. Define mock output for each asynchronous step in the orchestration. Optionally, define mock output for synchronous steps.
              1. On the Stages tab of the Debug panel, click Edit for a step.
                The Step properties panel opens to the Configure Test Output tab.
              2. On the Configure Test Output tab, set Define Test Output Values to On.
              3. Enter values for the step’s output values.
            3. Save the orchestration.
              Note
              Note If you’re debugging an activated orchestration you can save the automation only as a new orchestration.

            Start the Orchestration Run

            Debug the orchestration run and view its results in the Details tab of the Debug pane.

            1. On the Debug panel, click the Setup tab, and then click Run.
              The Details tab of the Debug panel shows cards for the orchestration run details.
            2. Review the debug details. To see more information about a card, in the card, click Details.
            3. To make and save changes to the orchestration, click Edit Flow.
              The Debug pane closes.
             
            Loading
            Salesforce Help | Article