When a manually triggered task runs, it generates a manually triggered instance. View and manage these instances in Operation Center — either in a list or a Directed Acyclic Graph (DAG) view.
Monitoring alerts are supported only for recurring instances. Manually triggered instances, data backfill instances, and test instances do not support monitoring alerts.
Intelligent Diagnosis features for manually triggered instances require DataWorks Professional Edition or later.
Navigate to the manually triggered instances page
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose Data Development and O&M > Operation Center. Select the desired workspace from the drop-down list and click Go to Operation Center.
In the left-side navigation pane, click Manually Triggered Node O&M > Manual Triggered Instances.
Manage instances
Operation Center groups manually triggered instances into three categories, each on a separate tab:
| Tab | Source |
|---|---|
| Manual Triggered Instances | One-time tasks run from Manage one-time tasks |
| Triggered Workflow Instance | Workflows triggered manually via Manage trigger-based workflows or via an event trigger |
| Instance in Manually Triggered Workflow | Manually triggered workflows run from Manage manually triggered workflows |
Manually triggered instances
On the Manual Triggered Instances tab, filter instances by Task Name, Task Type, or Data Timestamp.
Available actions:
Individual action: In the Actions column, click Stop or Rerun. Click More to view the runtime log and other details.
Rerun is only available for instances in the Succeeded or Failed state.
Bulk action: Select multiple instances, then click Stop or Rerun at the bottom of the page.
Export: After filtering, click Export Query Results to download the results to a local file. Export runs asynchronously — check progress and download the file from the View Operation Center action logs page.
DAG: Click an instance name or DAG in the Actions column to open the DAG view. See Manage the instance DAG.
Triggered workflow instances
On the Triggered Workflow Instance tab, filter instances by Task Name, Trigger, or Data Timestamp.
The Trigger column indicates how the workflow was started:
-— Started manuallyTrigger name — Started by an event trigger
Available actions:
Individual action: In the Actions column, click Stop or Rerun. Click More > Edit Node to edit the node in Data Studio.
Bulk action: Select multiple instances, then choose from the following at the bottom of the page: Stop, Batch Rerun, Set to Succeeded, Modify Priority, Modify Resource Group, or Refresh Instance.
Export: After filtering, click Export Query Results to download the results to a local file. Export runs asynchronously — check progress and download the file from the View Operation Center action logs page.
DAG: Click an instance name or DAG in the Actions column to open the DAG view. See Manage the instance DAG.
The icons below the task instance name indicate run status:
: Running instances
: Succeeded instances
: Failed instances
: Instances that have not run
Instances in manually triggered workflows
On the Instance in Manually Triggered Workflow tab, filter instances by Workflow, Status, or Data Timestamp.
Available actions:
Individual action: In the Actions column, click Stop or Rerun.
Rerun is only available for instances in the Succeeded or Failed state.
Bulk action: Select multiple instances, then choose from the following at the bottom of the page: Stop, Rerun, Set to Succeeded, Modify Priority, Modify Resource Group, or Refresh Instance.
Export: After filtering, click Export Query Results to download the results to a local file. Export runs asynchronously — check progress and download the file from the View Operation Center action logs page.
DAG: Click an instance name or DAG in the Actions column to open the DAG view. See Manage the instance DAG. Click a workflow in the list to display its DAG on the right — the DAG may contain multiple tasks.
The icons below the workflow name indicate run status:
- : Running instances
- : Succeeded instances
- : Failed instances
- : Instances in other states
Chained post-operation actions
Chained post-operation actions are supported only for triggered workflow instances.
When you modify a property (such as priority or resource group) on an instance that is already in the scheduling queue, the change does not apply to the currently running instance. Traditionally, you would stop the instance, apply the change, then rerun it manually. The post-operation action feature automates this Stop-Modify-Rerun sequence in a single step.
Modify priority, resource group, or refresh instance
When performing Modify Priority, Modify Resource Group, or Refresh Instance on triggered workflow instances, add a post-operation action to make the change take effect immediately.
Steps:
On the Triggered Workflow Instance tab, select one or more instances.
Click Modify Priority, Modify Resource Group, or Refresh Instance at the bottom of the page.
In the dialog box, configure the main operation, then expand the Post-operation Action section.
Post-operation action options:
| Option | What it does | When to use it |
|---|---|---|
| Stop instances that are in the Waiting for Time, Waiting for Resource, or Running state | After modifying the properties, automatically stops all target instances in the Waiting for Time, Waiting for Resource, or Running state. | You want to stop queued or running instances so they don't consume resources with outdated configurations. Decide whether to rerun them manually based on business needs. |
| Rerun Instance | After modifying the properties, immediately reruns all selected instances with the new configuration. | You want the changes (new priority, new resource group, or refreshed code) to take effect right away without manually stopping and rerunning. |
Stop instances
When stopping triggered workflow instances in bulk, chain an automatic rerun for rapid fault recovery.
Steps:
On the Triggered Workflow Instance tab, select one or more instances to stop.
Click Stop at the bottom of the page.
In the dialog box, expand the Post-operation Action section.
Post-operation action options:
| Option | What it does | When to use it |
|---|---|---|
| Rerun Instance | After stopping all selected instances, immediately reruns them. | A task is stuck or running too long. Stop it and restart it with the original configuration. |
| Reset Instance Status Before Rerunning | Forcibly resets all selected instances to Not Run status, then reruns them — even if they are currently running. | An instance's internal state is corrupted and a simple stop-and-rerun cannot resolve the issue. Use this to restart from a clean initial state. |
Manage the instance DAG
Click an instance name or DAG in the Actions column to open the DAG for that instance. Right-click an instance node in the DAG to access the following actions:
| Action | Description |
|---|---|
| Show Ancestor Nodes | Expands six levels of ancestor nodes for the selected node. Available only for instances in manually triggered workflows. |
| Show Descendant Nodes | Expands six levels of descendant nodes for the selected node. Available only for instances in manually triggered workflows. |
| View Runtime Log | Views the runtime log for the current instance, showing statuses such as Running, Succeeded, and Failed. |
| Instance Diagnose | Runs Intelligent Diagnosis to get end-to-end information about a task run and quickly locate issues. Requires DataWorks Professional Edition or later. |
| View Code | Views the code of the current node. |
| Edit Node | Opens the current workflow in Data Studio for editing. |
| View Data Lineage | Displays the data lineage of the current instance. |
| Stop | Stops the task. Valid only for the current instance. |
| Rerun | Reruns the task. Valid only for instances in the Succeeded or Failed state. |
Data retention
Instances cannot be deleted manually. The platform automatically deletes instances after they expire.
| Resource group type | Instance retention | Log retention | Notes |
|---|---|---|---|
| Shared Scheduling Resource Group | 1 month | 1 week | Logs larger than 3 MB for completed instances are cleared daily on a schedule. |
| Exclusive Scheduling Resource Group | 1 month | 1 month | — |