How to view and manage manually triggered instances - DataWorks

Manually triggered instances are generated when manually triggered tasks are run. You can view the details of and perform operations on manually triggered instances in the instance list or in the directed acyclic graph (DAG) of the instance.

Important

You can configure alert rules for the status of only auto triggered instances. You cannot configure alert rules for the status of manually triggered instances, data backfill instances, or test instances.
You must purchase DataWorks Professional Edition or a more advanced edition to use the instance diagnostics feature for manually triggered instances.

Go to the Manual Instance 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. On the page that appears, select the desired workspace from the drop-down list and click Go to Operation Center.
In the left-side navigation pane, choose Manual Triggered Node O&M > Manual Instance to go to the Manual Instance page.

Manage instances

You can view and manage manually triggered instances, event-triggered workflow instances, and manually triggered workflow instances.

Manage manually triggered instances

After you run a manually triggered task in Manage manually triggered tasks, a manually triggered instance is generated on the current page.

Go to the Manual Instance tab. You can filter and view information about manually triggered instances by specifying conditions such as Task Name, Task Type, and Business Time.
Perform operations on manually triggered instances.
- Individual operations: You can Stop or Rerun a manually triggered instance in the Actions column, or click More to view information such as instance run logs.
- Batch operations: You can select multiple manually triggered instances and then click the Stop or Rerun button at the bottom to perform batch operations on the manually triggered instances.
- DAG operations: You can perform related operations through Manage the DAG of a manually triggered instance.

Manage event-triggered workflow instances

You can manually run a workflow in Manage event-triggered workflows or run a workflow through Event trigger. After the workflow is triggered, the system generates a corresponding workflow instance on the current page.

Go to the Event-triggered Workflow Instance tab. You can filter and view information about event-triggered workflow instances by specifying conditions such as Task Name, Trigger, and Business Time.
Note
- Manually triggered: For event-triggered workflow instances that are manually triggered, the trigger is displayed as -.
- Event-triggered: For event-triggered workflow instances that are triggered by events, the name of the trigger is displayed.
Perform operations on event-triggered workflow instances.
- Individual operations: You can Stop or Rerun an event-triggered workflow instance in the Actions column, or click More > Edit Node to edit the event-triggered workflow instance in DataStudio.
- Batch operations: You can select multiple event-triggered workflow instances and then click the Stop or Batch Rerun button at the bottom to perform batch operations on the event-triggered workflow instances.
- DAG operations: You can perform related operations through Manage the DAG of a manually triggered instance.
You can understand the running overview information of the current instance by referring to the icons below the task instance.
- : The number of instances in the running state.
- : The number of instances that are successfully run.
- : The number of instances that failed to run.
- : The number of instances that are not run.

Manage manually triggered workflow instances

After you run a manually triggered workflow in Manage manually triggered workflows, a manually triggered workflow instance is generated on the current page.

Go to the Manual Workflow Instance tab. You can filter and view information about manually triggered workflow instances by specifying conditions such as Workflow, Running Status, and Business Time.
Perform operations on manually triggered workflow instances.
- Individual operations: You can Batch Stop or Rerun a manually triggered workflow instance in the Actions column.
- Batch operations: You can select multiple manually triggered workflow instances and then click the Stop or Batch Rerun button at the bottom to perform batch operations on the manually triggered workflow instances.
- DAG operations: You can perform related operations through Manage the DAG of a manually triggered instance.
You can understand the running overview information of the current workflow instance by referring to the icons below the manually triggered workflow.
- : The number of instances in the running state.
- : The number of instances that are successfully run.
- : The number of instances that failed to run.
- : The number of instances in states other than those mentioned above.

Manage the DAG of a manually triggered instance

Click the Instance Name or DAG in the Actions column to open the DAG of the current instance. In the DAG, you can right-click an instance to perform related operations. DAG

Note

In the list of manually triggered workflows, click the name of a manually triggered workflow. The DAG of the workflow appears on the right. The workflow may contain multiple instances.

Operation	Description
Show Ancestor Nodes	You can view six level of ancestor instances of an instance. Note Only manually triggered workflow instances support showing ancestor node information.
Show Descendant Nodes	You can view six level of descendant instances of an instance. Note Only manually triggered workflow instances support showing descendant node information.
View Runtime Log	View the run logs of the instance in the Running, Successful, or Failed state. Note You cannot manually delete an instance. DataWorks automatically deletes the instance about 30 days after the instance expires. The instances of a task that runs on the shared resource group for scheduling can be retained for a month after they expire. The logs of the instances can be retained for a week. If the size of the logs generated for an instance exceeds 3 MB, the system clears the logs every day. The instances of a task that runs on an exclusive resource group for scheduling can be retained for a month after they expire. The logs of the instances can also be retained for a month.
Instance Diagnose	Track the status of the instance and identify problems. For more information, see Intelligent diagnosis.
View Code	View the code of the node instance.
Edit Node	Go to the DataStudio page to modify the content of the current workflow.
View Lineage	View the lineage of the instance.
Stop	Stop the instance.
Rerun	Rerun the instance if the instance fails or is not run as scheduled. Note You can rerun only instances in the Successful or Failed state.