Auto-triggered tasks run on a schedule — no manual action needed. The Auto-triggered Nodes page in Operation Center is where you monitor these tasks in production, inspect their dependencies, and perform operations like freezing, data backfill, and testing.
Prerequisites
Before you begin, ensure that you have:
-
Access to the DataWorks console
-
A workspace with deployed auto-triggered tasks
-
(Optional) DataWorks Professional Edition or higher to use node aggregation and downstream analysis features in the DAG
Limitations
Node aggregation, upstream analysis, and downstream analysis in the Directed Acyclic Graph (DAG) require DataWorks Professional Edition or higher. For upgrade information, see Editions.
Usage notes
-
Do not operate on the
WorkspaceName_rootnode. This is the root node of the workspace. All auto-triggered task instances depend on it. Freezing it stops all auto-triggered task instances from running. -
After deploying a task, verify the changes on the Auto-triggered Nodes page. A deployment may fail, be blocked, or produce an unexpected version. Check the DAG to confirm upstream and downstream dependencies are correct, and check the node details to confirm that scheduling parameters in the production environment match your expectations.
How it works
Auto-triggered tasks create and run instances automatically when scheduled conditions are met. Each day's instances are generated at 23:30 the previous night, so most task changes take effect at the next scheduled time rather than immediately.
When you run a task manually, you can use the Data Backfill or Test features to generate a Data Backfill Instance or a Test Instance for specific data processing or debugging. A Data Backfill instance is generated immediately based on the current task configuration and runs as soon as it is triggered. For operations such as creating, deploying, running, freezing, and decommissioning tasks, see Basic operations for auto-triggered tasks.
Go to the Auto-triggered Nodes page
-
Log on to the DataWorks console. In the top navigation bar, select the target region. In the left-side navigation pane, choose Data Development and O&M > Operation Center, then select the target workspace and click Go to Operation Center.
-
In the left-side navigation pane, choose Cycle Task Maintenance > Cycle Task. The Auto-triggered Nodes page displays the task list and DAG.
Find auto-triggered tasks
The Auto-triggered Nodes page provides two search modes: Intelligent Search and Filter.
Intelligent search
Intelligent Search parses a natural-language query and returns matching tasks automatically.
-
Click Intelligent Search in the filter box. In the dialog that appears, enter a query such as
sort by node typeand press Enter. -
To save the search criteria for reuse, click Unsaved View > Save as New View. Enter a View Name and click Save. The view is then available from the view search bar.
To edit or delete a saved view, hover over its name in the view search bar, click ..., and select Edit or Delete.
-
To switch to filter mode, press Esc or click Disable Intelligent Search.
Filter mode
Filter mode lets you narrow down the task list using specific criteria.
-
Simple filter: In the toolbar, select one or more criteria — Task Name/ID, Node Type, Expired Within Last 180 Days, or Referenced — to filter the list.
-
Advanced filter: Click Filter in the filter box to combine multiple conditions, such as Task Name/ID, Computing Resource Group Type, Baseline, and Priority, for a more precise search.
Keep the following node states in mind when filtering:
A frozen node is not automatically scheduled. It generates frozen instances that do not run and block their downstream dependencies.
An orphaned node has no parent nodes and is not scheduled automatically. If an orphaned node has many downstream dependencies, downstream task execution is affected. For details, see Handle orphaned nodes.
An expired node is outside its validity period. It does not generate instances and does not run.
Manage auto-triggered tasks
Single-task operations
Find the task in the list and use the options in the Actions column.
| Action | Description |
|---|---|
| DAG | Opens the DAG page for the task, showing upstream and downstream dependencies. See View the task DAG. |
| Test | Generates a test instance to verify whether the task runs as expected. View the test run status on the Test Instances page. See Run a test and view the test instance. Note
Test runs also generate business data. Use this with caution. |
| Data Backfill | Runs the task for a historical or future time range. Generates a data backfill instance viewable on the Data Backfill Instance page. See View and manage data backfill instances. |
| More > Freeze | Freezes the task when it and its downstream tasks do not need to run for a period. A frozen task generates instances that are also frozen — they do not run and block downstream dependencies. Note
Do not freeze the |
| More > Unfreeze | Restores a frozen task to an active state. |
| More > Change Owner | Changes the owner of the task. |
| More > Modify Scheduling Resource Group | Changes the resource group used to run the task. |
| More > Modify Tag | Modifies, adds, or unbinds tags for the task. To manage all tags centrally, go to the Tag Management page. |
| More > Configure Data Quality Rules | Sets up data quality rules to validate data during runtime. See Overview of data quality. |
| More > View Instances | Goes to the Auto-triggered Instances page for this task. |
| More > View Lineage | Displays the data lineage for the task. |
| More > View Cycle Task Details | Shows the basic properties of the task. See View node details. |
| More > Add Alert Rule | Creates a custom alert rule to monitor the task's daily run status. Rules are visible on the Alert Management > Rule Management page. See Manage custom alert rules. |
| More > Add Baseline | Adds the task to a baseline for monitoring. See Overview. |
Batch operations
Select multiple tasks in the list, then use the bulk operation options — such as Freeze or Unfreeze — that appear below the list.
View the task DAG
Click DAG in the Actions column for a task to open its DAG page. The DAG shows upstream and downstream dependencies for the task.
DAG panel features
| Feature | Description |
|---|---|
| Node aggregation icons (upper-left) | Aggregate nodes by Do not aggregate, Aggregate by workspace, Aggregate by owner, or Aggregate by priority. Requires DataWorks Professional Edition or higher. |
| Downstream analysis | When there are many tasks or levels in the hierarchy, use this to count the number of downstream tasks affected by the current task. Requires DataWorks Professional Edition or higher. |
| Display style icons (upper-right) | Adjust the visual layout of the DAG. |
DAG right-click operations
Right-click any node in the DAG to access the following options:
-
Show Ancestor Nodes: Expands upstream tasks level by level, up to six levels. Use this to identify which tasks affect the data output of the current task.
-
Show Descendant Nodes: Expands downstream tasks level by level, up to six levels. Use this to identify which tasks are affected by the data output of the current task.
-
View Code: Displays the task's code in the production environment. If the code is not as expected, confirm that the latest version has been successfully deployed. See Deploy tasks.
-
Edit Node: Opens the task in DataStudio.
For other operations, see Manage auto-triggered tasks.
View node details
Click a node in the DAG. In the information panel that appears, click Expand details to inspect scheduling parameters, resource group configuration, and code in the production environment.
| Tab | Description |
|---|---|
| General | Displays the scheduling properties of the task in the production environment. See Configure scheduling properties. If parameters in DataStudio do not match those in Operation Center, confirm that the task changes were successfully deployed. This tab also shows: Rule monitoring — monitoring rules associated with the task (click Create to quickly add a task run status rule; see Manage custom alert rules). Data quality monitoring rules are not shown here. Baseline monitoring — baselines associated with the task (click Create to add a baseline; see Manage baselines). Baseline rule configurations appear on the Auto-triggered Nodes page the next day; to confirm same-day baseline creation, check Intelligent O&M > Manage Baselines. Maximum parallel instances — the maximum number of concurrent instances for the task (Unlimited or 1–10,000). This limit applies to all instance types for the same task: auto-triggered instances, data backfill instances, and test instances. |
| Operation log | Shows the operation history for the task, including time, operator, and action. |
| Code | Displays the latest code for the task in the production environment. If the code is not as expected, confirm that the latest version has been deployed. See Deploy tasks. |