> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Data Orchestration on a Deal

## Run Data Orchestration on a Deal

Run a published Data Orchestration template from a deal, review every evaluated attribute, and choose how to recover when a run stops.

## Before you begin

* The deal must be in its **Underwriting** stage.
* You need access to edit the deal's application and underwriting information and permission to run Data Orchestration.
* For client users, Data Orchestration management must be enabled for the client.
* The template must be published, available to your client, and compatible with the deal's workflow.

If the **Run Orchestration** control is missing or disabled, ask an administrator to confirm your role, client settings, and deal access. The control is also disabled while an orchestration is processing.

## 1. Run an orchestration

1. In the dashboard, open **Deals** and select the deal.
2. Open the deal's **Underwriting** stage.
3. In the **Data Orchestration** section, click the arrow on **Run Orchestration**.
4. Select a published template from the menu. Selecting the template starts the run.
5. Wait for the master status to move from **Processing** to its next state.

After the run starts, the Data Orchestration header shows the template name, log ID, and last-run time. The run menu is unavailable until processing finishes.

## 2. Review the result

Use the master status, outcome details, and issue banner together:

| Result | What it tells you |
| - | - |
| **Master status** | The current overall state of the orchestration: **Not Started**, **Processing**, **Review**, **Complete Pass**, **Complete Fail**, or **Error**. Authorized users can override some completed, review, or error states. |
| **Outcome** | The result produced when an individual block evaluates its conditions. Outcomes remain part of the run history and are not changed by a master-status override. |
| **Orchestration Outcome** | A dedicated view of the attributes checked during the run. Use its search, filters, source tabs, and expandable blocks to inspect returned and expected values. |

For a failed or manual-review run, the banner identifies the affected categories and attributes. Select an attribute in the banner to jump to its block in **Orchestration Outcome**. If more than two attributes are affected, select **and *n* more** to open the remaining attributes.

<Note>
  The failure or manual-review banner follows the current master status. Overriding the master status can clear that banner, but it does not rewrite the recorded block outcomes.
</Note>

## 3. Recover or run again

After a run has history, open the **Orchestration** menu and choose the action that matches your decision:

| Action | What it does | When it is available |
| - | - | - |
| **Pass-resume** | Continues from the last block along its configured pass path. | A pass next step exists, the latest outcome is not already pass or paused, and the master status is not **Complete Pass**. |
| **Fail-resume** | Continues from the last block along its configured fail path. | A fail next step exists and the latest outcome is not already fail or paused. |
| **Re-run Last Condition** | Retries the last orchestration step. | A previous run exists and its template has not been deleted. |
| **Restart Orchestration** | Runs the same template again from the beginning. | A previous run exists and its template has not been deleted. |
| **Run New Orchestration** | Opens the template list so you can start a different published template on the deal. | A previous run exists. |

If you run a data service manually outside the orchestration, its result is recorded as a manual run and does not resume or replace the orchestration's conditional path. Review the new data, then choose a recovery action or, if authorized, update the master status.

<Note>
  **API alternative:** Use [Retry Last Data Orchestration Step](/api-reference/data-orchestration/retry-last-data-orchestration-step), [Continue Data Orchestration as Pass](/api-reference/data-orchestration/continue-data-orchestration-as-pass), or [Continue Data Orchestration as Fail](/api-reference/data-orchestration/continue-data-orchestration-as-fail) to recover a run programmatically. Authorized integrations can use [Update Data Orchestration Master Status](/api-reference/data-orchestration/update-data-orchestration-master-status) to override the run's overall status.
</Note>

## FAQ

<AccordionGroup>
  <Accordion title="What do the provider icon borders mean?">
    A provider icon has no colored border until the provider has a result. Blue
    identifies a manual run, green identifies a pass, red identifies a fail,
    and orange identifies manual review. Select a provider tab or icon to inspect
    its results.
  </Accordion>

  <Accordion title="Can I open the template from the deal?">
    Yes, if you have permission to view that template. In the **Data
    Orchestration** header, select the template name or open-in-new-tab icon. The
    template opens in a new browser tab. Client users can view only templates
    available to their client.
  </Accordion>

  <Accordion title="Can I change the master status?">
    Some users can select the master-status pill and choose one of the allowed
    next statuses. Client users need underwriting-management and Data
    Orchestration-management access; basic client users and client analysts
    cannot make this change. The available choices depend on the current master
    status.
  </Accordion>

  <Accordion title="Why is Pass-resume or Fail-resume missing?">
    The action appears only when the last block has a configured next step for
    that outcome and the current run state allows it. A paused run does not show
    either resume action.
  </Accordion>

  <Accordion title="What does the master-status tooltip describe?">
    Hover over the master-status pill to see that it represents the current
    overall state of the orchestration and can map automatically as the flow
    progresses. If your permissions allow it, the pill also opens the available
    manual status transitions.
  </Accordion>
</AccordionGroup>

## Next steps

<Card title="Configure Custom Workflow Webhooks" icon="webhook" horizontal href="/lendflow-external/docs/custom-workflows-webhooks">
  Send workflow and Data Orchestration notifications to your integration.
</Card>