DataWorks generates manually triggered node instances from manually triggered nodes. Manually triggered nodes do not have node dependencies. They must be run manually.
Note Currently, DataWorks generates alerts only for auto triggered node instances. DataWorks
does not generate alerts for manually triggered node instances, retroactive instances,
or test instances.
Manage manually triggered node instances in the instance list
| Operation | Description |
|---|---|
| Filter | Find required instances by setting parameters in the red box marked with 1 in the
preceding figure.
You can search for instances by workflow name and set Type, Owner, Data Timestamp, and Run At to filter instances. |
| DAG | Click DAG in the Actions column to view the directed acyclic graph (DAG) of the instance. You can view the running result of the instance in the DAG. |
| Stop | Click Stop to stop the instance if it is in the Running state. |
| Rerun | Rerun the instance. |
| Batch operations | Select multiple instances and click Stop in the red box marked with 3 in the preceding figure to stop the selected instances at a time. |
Manage manually triggered node instances in a DAG
Click the name of an instance or DAG in the Actions column to view the DAG of the instance. In the DAG, you can right-click the instance to perform related operations.
Note A manually triggered workflow does not have dependencies, so only the current instance
appears in the DAG.
| Operation | Description |
|---|---|
| View Runtime Log | View the operational logs of the instance if it is in the Running, Successful, or Failed state. |
| View Code | View the code of the instance. |
| Edit Node | Go to the DataStudio page to modify the workflow to which the instance belongs. |
| View Lineage | View the lineage of the instance. |
| Stop | Stop the current instance of the workflow. |
| Rerun | Rerun the instance if it is in the Failed state or an abnormal state. |