An auto triggered node instance is a snapshot that is taken for an auto triggered node at the time when the node is scheduled to run. You can view the details about and perform the related operations on an auto triggered node instance in the list of auto triggered node instances or in the directed acyclic graph (DAG) of the instance.
Limits
- Only users of DataWorks Professional Edition or a more advanced edition can use the intelligent diagnosis feature. If you use another edition, you can have a trial use of the feature for free. However, we recommend that you upgrade the DataWorks service to DataWorks Professional Edition to use more features. For more information, see Instance diagnosis.
- Only users of DataWorks Professional Edition or a more advanced edition can use the aggregation, upstream analysis, and downstream analysis features provided by DAGs. For more information, see Billing of DataWorks advanced editions.
- Some features can be used only by users who are granted O&M permissions. If the entry point of a feature is dimmed or is not displayed, you can check whether you have the required O&M permissions on the Manage Members tab of the User Management page. For more information, see Manage workspace-level roles and members.
- You cannot manually delete an auto triggered node instance. DataWorks deletes an auto triggered node instance approximately 30 days after the instance expires. If you no longer need to run an auto triggered node instance, you can freeze it.
- Node instances that are run on the shared resource group for scheduling are retained for one month (30 days), and the run logs for the node instances are retained for one week (7 days).
- Node instances that are run on an exclusive resource group for scheduling are retained for one month (30 days), and the run logs for the node instances are also retained for one month (30 days).
- The system regularly clears excess run logs every day when the size of run logs generated for the auto triggered node instances that finish running exceeds 3 MB.
Precautions
- Instances are generated as scheduled for auto triggered nodes. Each generated instance runs the most recent code. If you modify and recommit the code of a node after instances are generated for the node, the instances that are not run will run the most recent code.
- If you want to monitor a node for which instances are generated, you must configure monitoring rules for the node first. If a node for which monitoring rules are configured fails to run and you do not receive an alert notification, check whether your mobile phone number and email address are configured on the Alert Contacts page. For more information, see View alert details.
- The time at which instances are generated for an auto triggered node varies based
on the value of the Instance Generation Mode parameter. The valid values of the Instance
Generation Mode parameter include Next Day and Immediately After Deployment. For more information, see Instance generation modes.
Note Nodes that are manually rerun do not trigger alerts generated based on custom rules.
Node instance running and issue troubleshooting
An auto triggered node instance can be scheduled to run only when the following conditions are met: Ancestor nodes of the node for which the auto triggered node instance is generated are successfully run, the scheduling time of the auto triggered node instance has arrived, scheduling resources are sufficient, and the auto triggered node instance is not frozen. For more information, see What are the conditions that are required for a node to successfully run?.
If an auto triggered node instance fails to run, you can use the ancestor node analysis feature on the Upstream Analysis tab of the DAG page to quickly identify ancestor node instances that block the running of the current node instance. Then, you can use the intelligent diagnosis feature to diagnose failure causes or related issues of the ancestor node instances. The intelligent diagnosis feature can also be used to quickly troubleshoot issues when dependencies between the current node instance and ancestor node instances are complex. This improves O&M efficiency.
View auto triggered node instances

Operation | Description |
---|---|
Filter | Allows you to specify conditions to search for auto triggered node instances in the
area marked with 1 in the preceding figure.
You can search for auto triggered node instances by node name or node ID. You can also specify the following conditions to search for auto triggered node instances: Data Timestamp, Data Timestamp, Node Type, Run At, Solution, Workflow, Region, Scheduling Resource Group, Engine Type, Engine Instance, Baseline, Owner, Scheduling Type, Status, My Nodes, My Nodes with Errors, My Incomplete Nodes, Rerun Nodes, Slow Nodes, and Nodes that generated alarms in the past 24 hours. Note
|
List of instances | Allows you to view the auto triggered node instances that meet the specified conditions in the area marked with 2 in the preceding figure. |
Actions | Allows you to perform operations on an auto triggered node instance in the area marked
with 3 in the preceding figure.
|
Batch operations | Allows you to perform operations on multiple auto triggered node instances at the same time. You can click the following buttons in the area marked with 4 in the preceding figure to perform operations on multiple auto triggered node instances at the same time: Stop, Rerun, Set Status to Successful, Freeze, and Unfreeze. |
Items per page | Allows you to select the number of items that you want to view on a single page in the area marked with 5 in the preceding figure. The maximum number that you can select is 200. |
Manage auto triggered node instances in a DAG

Functionality | Description |
---|---|
Operations that you can perform on the DAG page | You can click DAG in the Actions column of an auto triggered node instance to open the DAG of the auto
triggered node instance. You can perform the following operations in the DAG of the
auto triggered node instance:
|
Operations on a single instance | You can right-click your desired auto triggered node instance in a DAG and perform
operations on the instance.
Note For information about other operations, see View auto triggered node instances.
|
Details about a single instance | In the area marked with 5 in the preceding figure, you can perform the following operations:
|
View the details about an auto triggered node instance

Tab | Description |
---|---|
General | On this tab, you can view the scheduling properties of an auto triggered node instance
in the production environment. For more information about the basic parameters, see
Configure basic properties.
Note
|
Context | On this tab, you can view all input and output parameters of the node for which an auto triggered node instance is generated. For more information, see Configure input and output parameters. |
Runtime Log | On this tab, you can view the running details about an auto triggered node instance. |
Operation Log | On this tab, you can view the operation records of a node or an instance, including the operation time, operator, and specific operations. |
Code | On this tab, you can view the latest code of the node for which the current auto triggered node instance is generated in the production environment. If the code of the node does not meet your expectations, you must check whether the latest code of the node is successfully deployed to the production environment. For more information, see Deploy nodes. |
FAQ
- Troubleshoot instance exceptions
- What do I do if I cannot find the desired auto triggered node on the Cycle Task page in Operation Center?
- Why cannot I find even one instance of an auto triggered node?
- What do I do if I can find instances of other auto triggered nodes but cannot find even one instance of the desired auto triggered node?
- What do I do if the desired auto triggered node has instances but the instances are not run?
- What are the conditions that must be met to run a node?
- Troubleshoot issues for pending nodes