---
schema_version: "1"
id: 8a1ef87381dbcf4f71ad5ea1afe4a1a865d41c5ec3f4046f27a1091a07cd8052
title: Orchestration Run
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/orchestrator_orchestration_run.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.orchestrator_orchestration_run.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: f131fb8f63aaa39851c071cbc8652ff68dd23dff39def2b444e479a8887a1778
description: An orchestration run represents an instance of a running orchestration.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Orchestration Run

An orchestration run represents an instance of a running orchestration.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.automate_orchestrator_about_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Review the supported products and editions for Flow Orchestration.">View supported editions for Flow Orchestration.</a></td></tr></tbody></table>

An orchestration is an application built by your admin that uses stages, steps, and decisions to organize a complex business process.An orchestration run is a run-time instance of an active orchestration. Starting in API version 60.0, all orchestrations run in system context without sharing. For earlier API versions, the context that an orchestration run uses depends on the orchestration type. You can also specify the context by using the Advanced option How to Run the Orchestration. See [Flow Orchestration Version Properties](https://help.salesforce.com/s/articleView?id=platform.orchestrator_ref_properties.htm&release=264.0.0&type=5 "An orchestration version’s properties consist of its label and description. These values drive the field values that appear on the orchestration’s detail page.").

## Orchestration Run Lifecycle

![The lifecycle for an orchestration run](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/orchestration/orchestrator_orchestration_work_cycle.png)

## Resuming a Failed Orchestration

For information about configuring fault paths and error handling strategies, see [Error Handling in Orchestrations](https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_error_handling.htm&release=264.0.0&type=5 "Error handling manages unexpected issues that occur in stages during an orchestration run. Configure fault paths for stages to define recovery actions when stage errors occur, ensuring orchestrations complete successfully instead of failing.").

An orchestration run can't recover from all errors that occur during its execution. Whether you can resume a failed orchestration run depends on where the error occurred.

Resuming requires an administrator to fix the underlying flow or error and then resume the orchestration run. This approach differs from fault paths, which an orchestration designer configures at design time. Fault paths handle errors gracefully and provide recovery mechanisms or manual intervention steps for end users.

Recoverable errors occur in two scenarios, and you have up to 14 days to fix these errors and resume the orchestration run.

- A flow called by a background or interactive step encounters an error.
- A step has a frozen or inactive assignee.

Non-recoverable errors occur in three scenarios, and you can't resume the errored orchestration run.

- An error occurs outside of the flows that steps call, such as when the orchestration prepares requests or processes results.
- An error occurs in an action called by a MuleSoft step.
- A step has an incorrectly configured assignee, such as a resource variable that doesn't resolve to a valid user, group, or queue.

When an orchestration run encounters an error, the system sets the status of affected orchestration runs, stage runs, and step runs.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><colgroup><col style="width:50%"> <col style="width:50%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Item</td><td class="slds-cell-wrap" style="vertical-align:top;">Status Set To</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Orchestration run</td><td class="slds-cell-wrap" style="vertical-align:top;">Error</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Current stage run</td><td class="slds-cell-wrap" style="vertical-align:top;">Error</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Errored step run</td><td class="slds-cell-wrap" style="vertical-align:top;">Error</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">In-progress step runs</td><td class="slds-cell-wrap" style="vertical-align:top;">Discontinued</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Work items with an Assigned status</td><td class="slds-cell-wrap" style="vertical-align:top;">Completed</td></tr></tbody></table>

If the error is recoverable, you fix the error in the flow and then resume the failed orchestration. When you resume, the system restarts the errored step. For background steps, the system re-runs the step with the fixed autolaunched flow. For interactive steps, the system creates another work item, and the assignee completes the step by using the fixed screen flow. See [Resume a Failed Orchestration](https://help.salesforce.com/s/articleView?id=platform.orchestrator_manage_resume_failed_orchestration.htm&release=264.0.0&type=5 "When an orchestration run failed within the previous 14 days because of an error in an action called by a step, you can fix the error and resume the orchestration.").

Resuming also affects discontinued steps from the current stage. For discontinued background or MuleSoft steps, if the step has no pending outputs, the system restarts the step. For discontinued interactive steps from the current stage, the system creates a replacement work item. If any discontinued step has pending outputs, the system processes the stored outputs and doesn't restart the step.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:25%">
          <col style="width:25%">
          <col style="width:25%">
          <col style="width:25%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e226">Item</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e229">Status in Failed Run</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e232">When Run Is Resumed</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e235">Status in Resumed Run</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Item" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e226 ">Stage</td>

            <td data-label="Status in Failed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e229 ">Error</td>

            <td data-label="When Run Is Resumed" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e232 ">The stage resumes.</td>

            <td data-label="Status in Resumed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e235 ">In Progress</td>

          </tr>
          <tr class="">
            <td data-label="Item" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e226 ">Background or MuleSoft Step</td>

            <td data-label="Status in Failed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e229 ">Error</td>

            <td data-label="When Run Is Resumed" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e232 ">The step restarts.</td>

            <td data-label="Status in Resumed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e235 ">In Progress</td>

          </tr>
          <tr class="">
            <td data-label="Item" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e226 ">Background or MuleSoft Step</td>

            <td data-label="Status in Failed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e229 ">Discontinued (no pending outputs)</td>

            <td data-label="When Run Is Resumed" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e232 ">The step restarts.</td>

            <td data-label="Status in Resumed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e235 ">In Progress</td>

          </tr>
          <tr class="">
            <td data-label="Item" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e226 ">Background or MuleSoft Step</td>

            <td data-label="Status in Failed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e229 ">Discontinued (pending outputs)</td>

            <td data-label="When Run Is Resumed" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e232 ">The stored outputs are processed, and the step doesn’t restart.</td>

            <td data-label="Status in Resumed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e235 ">
              <p>Completed</p>
              <p style="margin-bottom:0;">Error</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Item" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e226 ">Interactive Step</td>

            <td data-label="Status in Failed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e229 ">
              <p>Error</p>
              <p style="margin-bottom:0;">Discontinued</p>
            </td>

            <td data-label="When Run Is Resumed" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e232 ">A replacement work item is created for the step.</td>

            <td data-label="Status in Resumed Run" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e235 ">In Progress</td>

          </tr>
        </tbody>
      </table>

## Fault Paths in Orchestration Runs

Fault paths provide error handling when an error occurs in a stage. When a stage has an attached fault path and an error occurs during processing, the orchestration follows the fault path. This approach to error handling provides an alternative to immediately terminating with a status of Error.

Fault paths are useful in scenarios where end users can provide manual intervention when the orchestration run encounters an error. For example, an external integration or API call fails because an endpoint is down. A fault path can include an interactive step where the assignee manually enters the required data.

What happens next depends on the fault path configuration. Fault paths containing elements run those elements. If the fault path terminates with an End element and no unhandled errors occur, the orchestration run ends with Completed status. An unhandled error in the fault path causes the orchestration run to end with a status of Error.

If the fault path connects back into the orchestration, the orchestration continues to run. It runs until completion or until an unhandled error occurs. This behavior is true whether the fault path contains elements or not. When an empty fault path connects back into the orchestration, the next element runs without any intervening processing.

The orchestration doesn't send error notifications when a fault path handles an error. However, you can add a background step to the fault path that notifies stakeholders when a failure occurs. The flow or action that encounters the error handles its own error notifications based on its error handling configuration.

For more information about fault paths in orchestrations, see [Error Handling in Orchestrations](https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_error_handling.htm&release=264.0.0&type=5 "Error handling manages unexpected issues that occur in stages during an orchestration run. Configure fault paths for stages to define recovery actions when stage errors occur, ensuring orchestrations complete successfully instead of failing.").

## Statuses and Milestones

After it’s created, an orchestration run has an associated status.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e379">Orchestration Run Status</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e382">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Orchestration Run Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e379 ">In Progress</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e382 ">The orchestration run started.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e379 ">Completed</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e382 ">
              <ul>
                <li>The orchestration run was completed without error.</li>

                <li>The orchestration run encountered an error that was handled by a configured
                  fault path.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e379 ">Suspended</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e382 ">The orchestration run was manually suspended.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e379 ">Canceled</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e382 ">The orchestration run was manually canceled.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Status" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e379 ">Error</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e382 ">
              <ul>
                <li>The orchestration run encountered an error.</li>

                <li>A stage within the orchestration run encountered an error.</li>

                <li>A step within the orchestration run encountered an error.</li>

                <li>The screen flow or autolaunched flow associated with a step within the
                  orchestration run encountered an error.</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

In logging, an orchestration run has several milestones.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e476">Orchestration Run Milestone</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d254858e479">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Orchestration Run Milestone" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e476 ">Start Run</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e479 ">The orchestration run started or was manually resumed.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Milestone" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e476 ">End Run</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e479 ">The orchestration run was completed.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Milestone" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e476 ">Suspend Run</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e479 ">The orchestration run was manually suspended.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Milestone" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e476 ">Cancel Run</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e479 ">The orchestration run was manually canceled.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Milestone" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e476 ">Resume Run</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e479 ">The orchestration run was manually resumed.</td>

          </tr>
          <tr class="">
            <td data-label="Orchestration Run Milestone" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e476 ">Fail Run</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d254858e479 ">
              <ul>
                <li>The orchestration run encountered an error.</li>

                <li>A stage within the orchestration run encountered an error.</li>

                <li>A step within the orchestration run encountered an error.</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

#### See Also

- [Running Context of an Orchestration](https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_running_user.htm&release=264.0.0&type=5 "The running context determines the access that an orchestration has to Salesforce data and the context used by a paused orchestration to resume. By default, the running context of an orchestration is the Automated Process User in system context.")