Auto triggered nodes are automatically run as scheduled after they are committed to the scheduling system. You can view the details of an auto triggered node and perform operations on the node in the auto triggered node list or in the directed acyclic graph (DAG) of the node on the Cycle Task page.
Background information
- For more information about how to create, deploy, run, or undeploy an auto triggered node, or suspend the scheduling of an auto triggered node, see the topic that provides an O&M overview of auto triggered nodes.
- DataWorks automatically generates auto triggered node instances that are scheduled to run on the next day for an auto triggered node every night. You can click Backfill Data or Test in the Actions column of the node to generate a data backfill instance or a test instance for the node. You can view the status of the generated instances.
Limits
Only users of DataWorks Professional Edition or a more advanced edition can use the node aggregation, ancestor node analysis, and descendant node analysis features provided on the DAG page. For more information about how to update DataWorks, see DataWorks advanced editions.
Precautions
- Do not freeze the projectname_root node, which is the root node of a workspace. Instances of auto triggered nodes depend on this node. If this node is frozen, the instances of auto triggered nodes cannot be run.
- After you modify an auto triggered node, you must deploy the node. After the node
is successfully deployed, the modification takes effect in the production environment.
You may encounter the following unexpected situations when you deploy the node: The
node fails to be deployed, the deployment process is blocked, or the version of the
deployed node does not meet your expectations. In these cases, we recommend that you
go to the Cycle Task page in Operation Center to troubleshoot issues.
- You can use the DAG of a node to check whether dependencies of the node are correct.
- You can view the information on the details page of a node to check whether parameter configurations for the node in the production environment meet your business requirements.
Go to the Cycle Task page
- Log on to the DataWorks console.
- In the left-side navigation pane, click Workspaces.
- In the top navigation bar, select the region where the workspace that you want to
manage resides. Find the workspace, move the pointer over the
icon in the Actions column of the workspace, and then select Operation Center.
- In the left-side navigation pane of the page that appears, choose Cycle Task page, view the auto triggered node list or the DAG of an auto triggered node. . On the
View the auto triggered node list

Operation item | Description |
---|---|
Filter | Allows you to specify conditions to search for your desired node in the rectangle
marked with 1 in the preceding figure.
You can search for your desired node by node name or node ID. You can also specify the following conditions to search for your desired node: Solution, Workflow, Node Type, Owner, Region, Scheduling Resource Group, Engine Type, Engine Instance, Baseline, My Nodes, Modified Today, Frozen Nodes, Isolated Nodes, and Expired Nodes.
Note
|
Auto triggered node list | Allows you to view the auto triggered nodes that meet the specified conditions in the rectangle marked with 2 in the preceding figure. |
Operations on a single node | Allows you to perform operations on an auto triggered node in the rectangle marked
with 3 in the preceding figure.
|
Batch operations | Allows you to perform an operation on multiple auto triggered nodes at the same time. You can click the following buttons in the rectangle marked with 4 in the preceding figure to perform operations on the selected nodes at the same time: Change Owner, Modify Scheduling Resource Group, Modify Data Integration Resource Group, Freeze, Unfreeze, Configure Alert Rule, Add to Baseline, and Undeploy. |
Items per page | Allows you to select the number of items that you want to view on a single page in the rectangle marked with 5 in the preceding figure. The maximum number that you can select is 200. |
View the DAG of an auto triggered node

Functionality | Description |
---|---|
Operations that you can perform on the DAG page | Allows you to use the node aggregation and descendant node analysis features and adjust the display style of the DAG of a node by clicking icons and buttons in the rectangles marked with 1 in the preceding
figure. For more information, see Manage instances in a DAG.
|
Operations on a single node | Allows you to perform related operations on an auto triggered node in the DAG of the
node in the rectangle marked with 2 in the preceding figure.
Note For information about other operations, see View the auto triggered node list.
|
Details about a single node | Allows you to view properties of an auto triggered node in the rectangle marked with 3 in the preceding figure. You can also click Show Details to view the property details, context parameters, operation logs, and code of the node. For more information, see View the details of an auto triggered node. |
View the details of an auto triggered node
On the tabs that appear after you click Show Details, you can view properties such as scheduling parameters of and resource groups that are used by an auto triggered node in the production environment and check whether the code of the node meets your expectations.

Tab | Description |
---|---|
General | On this tab, you can view the scheduling properties of an auto triggered node in the
production environment. For more information about the basic parameters, see Configure basic properties.
Note If the parameter configurations for an auto triggered node on the DataStudio page
are inconsistent with those for the node on the Cycle Task page in Operation Center,
we recommend that you check whether you successfully deploy the node after you modify
the node.
|
Context | On this tab, you can view the input and output parameters of an auto triggered node. For more information about the context parameters, see Configure context-based parameters. |
Operation Log | On this tab, you can view operation records of an auto triggered node, including the operation time, operator, and specific operations. |
Code | On this tab, you can view the latest code of an auto triggered node in the production environment. If the code of the node does not meet expectations, you need to confirm whether the latest code of the node is successfully deployed to the production environment. For more information, see Deploy nodes. |