Skip to main content

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: 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.
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.

3. Recover or run again

After a run has history, open the Orchestration menu and choose the action that matches your decision: 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.
API alternative: Use Retry Last Data Orchestration Step, Continue Data Orchestration as Pass, or Continue Data Orchestration as Fail to recover a run programmatically. Authorized integrations can use Update Data Orchestration Master Status to override the run’s overall status.

FAQ

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.
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.
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.
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.
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.

Next steps

Configure Custom Workflow Webhooks

Send workflow and Data Orchestration notifications to your integration.