View and manage auto triggered tasks - DataWorks - Alibaba Cloud Documentation Center

Auto triggered tasks are automatically run as scheduled after they are committed to the scheduling system. You can view the list of auto triggered tasks in a workspace, view the configurations of auto triggered tasks that are deployed in the production environment, and manage auto triggered tasks on the Auto Triggered Nodes page in Operation Center.

Background information

In DataWorks, auto triggered tasks are automatically scheduled by the system based on scheduling settings. You can view the auto triggered tasks on the Auto Triggered Nodes page in Operation Center. Auto triggered tasks can also be manually triggered. If you want to manually trigger an auto triggered task, you can backfill data for or test the task. Then, the system generates a data backfill instance or a test instance for the task. You can use the data backfill instance or test instance to perform data processing or debugging. If an auto triggered task meets specified conditions, the system automatically generates auto triggered instances for the task at 23:30 every night and runs the instances on the next day.

If you modify an auto triggered task that is deployed to the production environment, the modifications take effect on the instances that are generated for the task after the modification is complete. In most cases, the modification on an auto triggered task takes effect when the scheduling time of the task on the next day arrives. For example, if you deploy an auto triggered task whose scheduling time is set to a point in time on the next day, the system generates auto triggered instances for the task at 23:30 on the current day and runs the instances at the scheduling time on the next day. If you backfill data for an auto triggered task, the system immediately generates a data backfill instance for the task based on the configurations of the task and the data backfill instance immediately takes effect after you manually trigger it. For information about operations such as creation, deployment, running, suspending, and undeployment, see Perform basic O&M operations on auto triggered tasks.

Limits

Only users of DataWorks Professional Edition or a more advanced edition can use the aggregation, upstream analysis, and downstream analysis features provided by directed acyclic graphs (DAGs). For information about billing rules for upgrading the edition of the DataWorks service, see Billing of DataWorks editions.

Precautions

Do not freeze the task that is named in the Workspace name_root format. The task is the root task of your workspace. All instances of auto triggered tasks depend on this task. If this task is frozen, the instances of auto triggered tasks cannot be run.
After you modify an auto triggered task, you must deploy the task. After the task is successfully deployed, the modification takes effect in the production environment. The following exceptions may occur when you deploy the auto triggered task: The task fails to be deployed, the deployment process is blocked, or the version of the deployed task does not meet your expectations. In these cases, we recommend that you go to the Auto Triggered Nodes page in Operation Center to troubleshoot issues.
- You can check whether the dependencies of the auto triggered task are correct in the DAG of the task.
- You can view the information on the details page of the auto triggered task to check whether the parameter configurations of the task in the production environment meet your business requirements.

Go to the Auto Triggered Nodes 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 of the Operation Center page, choose Auto Triggered Node O&M > Auto Triggered Nodes. On the Auto Triggered Nodes page, view the list of auto triggered tasks or the DAG of an auto triggered task.

View an auto triggered task

The Auto Triggered Nodes page displays all tasks that are committed to the scheduling system. You can click Intelligent Search and specify a filter condition to search for the desired auto triggered tasks. You can also directly specify filter conditions to search for the desired auto triggered tasks.

Search for auto triggered tasks by using the Intelligent Search feature

The Auto Triggered Nodes page provides the Intelligent Search feature. After you click Intelligent Search and select or enter a filter condition, the system automatically displays the auto triggered tasks that meet the filter condition.

Perform a search by using the Intelligent Search feature.
In the upper part of the Auto Triggered Tasks page, click Intelligent Search. In the search box that appears, enter or select a filter condition and press Enter. Then, the system automatically displays the auto triggered tasks that meet the filter condition. For example, you can enter the filter condition Sorting by task type.
Save a view.
If you want to continue using a filter condition in subsequent operations, perform the following steps to save the list of auto triggered tasks that are displayed after the filtering as a new view: Click Unsaved View, and select Save as New View in the drop-down list. In the Save View dialog box, configure the View Name parameter and click Save. Then, you can find the view in the view search drop-down list and use the view to search for desired auto triggered tasks.
Note
If you no longer require the view, you can find it in the view search drop-down list, move the pointer over the More icon next to the view name, and then select Edit or Delete to modify or delete the view.
Disable the Intelligent Search feature.
If you want to perform an exact match based on filter conditions, press Esc or click Disable Intelligent Search to exit the intelligent search mode.

Search for auto triggered tasks by directly specifying filter conditions

You can use the filter conditions that are displayed on the Auto Triggered Nodes page to search for the desired auto triggered tasks.

Perform a search based on simple filter conditions.
Specify a task name or task ID or select filter conditions such as Node Type, Expired Within Last 180 Days, and Referenced to search for the desired auto triggered tasks.
Perform a search based on complex filter conditions.
Click the Filter icon. In the dialog box that appears, specify a task name or task ID or configure filter conditions such as Computing Resource Type, Baselines, and Priority to search for the desired auto triggered tasks.

Note

Frozen task: A frozen auto triggered task is not automatically scheduled, and its descendant tasks are blocked from running. If an auto triggered task is frozen, instances generated for the task are also frozen. Frozen instances are not automatically scheduled, and the descendant tasks of the auto triggered task are blocked from running.
Isolated task: An isolated task does not depend on another task. This type of task is not automatically scheduled. If an isolated task has a large number of descendant tasks, the running of the descendant tasks is affected. For more information, see Scenario: Isolated node.
Expired task: An expired task does not generate instances and is not run.

Manage auto triggered tasks

Manage a single task

If you want to manage a single auto triggered task, find the task on the Auto Triggered Nodes page and click the related entry points for different features in the Actions column.

Feature		Description
DAG		The DAG of an auto triggered task displays the dependencies of the task. You can perform operations on the auto triggered task in the DAG of the task. For more information, see View the DAG of an auto triggered task.
Test		This feature allows you to test whether the running of an auto triggered task meets expectations. After you click Test in the Actions column of the task, a test instance is generated for the task. You can go to the Test Instances page to view the status of the test instance. For more information, see Test an auto triggered task and view test instances generated for the task. Note A test instance generates data. Perform this operation only when it is necessary.
Backfill Data		This feature allows you to backfill data for an auto triggered task for a period of time in the past or in the future. After you backfill data for the auto triggered task, a data backfill instance is generated for the task. You can go to the Data Backfill page to view the status of the data backfill instance. For more information, see Backfill data and view data backfill instances (new version).
More	Freeze	If you do not want an auto triggered task and its descendant tasks to run for a period of time, you can click Freeze to freeze the tasks. The instance generated for a frozen auto triggered task is also in the frozen state. The frozen instance is not run and blocks the running of its descendant tasks. Note Do not freeze the task that is named in the `Workspace name_root` format. The task is the root task of your workspace. All instances of auto triggered tasks depend on this task. If this task is frozen, the instances of auto triggered tasks cannot be run.
	Unfreeze	This feature allows you to resume a frozen auto triggered task.
	Change Owner	This feature allows you to change the owner of an auto triggered task.
	Modify Scheduling Resource Group	This feature allows you to change the resource group for scheduling used to run an auto triggered task.
	Modify label	This feature allows you to add tags to, remove tags from, or modify tags that are added to an auto triggered task. For more information about how to manage tags for an auto triggered task, see Manage tags.
	Configure Data Quality Rules	This feature allows you to configure a data quality monitoring rule for an auto triggered task to check data quality of the task when the task is run. For more information, see Overview.
	View Instances	This feature allows you to view the auto triggered instances generated for an auto triggered task on the Auto Triggered Instances page.
	View Lineage	This feature allows you to view the data lineage of an auto triggered task.
	View cycle task details	This feature allows you to view basic properties of an auto triggered task. For more information about related parameters, see View the details of an auto triggered task.
	Add Alert Rule	This feature allows you to configure a custom alert rule to monitor the status of an auto triggered task every day. After the configuration is complete, you can choose Alarm > Rule Management in the left-side navigation pane of the Operation Center page to view the configured custom alert rule. For more information, see Create a custom alert rule.
	Add Baseline	This feature allows you to associate an auto triggered task with a baseline. For information about baselines, see Overview.

Manage multiple auto triggered tasks at a time

If you want to manage multiple auto triggered tasks at a time, you can select the tasks on the Auto Triggered Nodes page, and click the entry points for operations such as Freeze and Unfreeze in the lower part of the page.

View the DAG of an auto triggered task

If you want to view the DAG of an auto triggered task, you can find the task on the Auto Triggered Nodes page and click DAG in the Actions column.

Features in the DAG of an auto triggered task

The following table describes the features provided in the DAG of an auto triggered task.

Feature (represented by icons)		Description
		You can click the icons in the upper-left corner of the DAG of an auto triggered task to aggregate task information from one of the following dimensions or cancel aggregation: Not Aggregate Aggregate By Workspace Aggregate By Owner Aggregate By Priority



		If an auto triggered task has multiple descendant tasks or the descendant tasks of an auto triggered task are distributed at multiple levels, you can use the Downgrade Analysis feature to calculate the number of descendant tasks that are affected by the current task.
		You can click the icons in the upper-right corner of the DAG of an auto triggered task to adjust the display style of the DAG.

Operations that you can perform in the DAG of an auto triggered task

In the DAG of an auto triggered task, you can right-click the task name to perform different operations. Example:

Show Ancestor Nodes: View the ancestor tasks of an auto triggered task at different levels. A maximum of six levels of ancestor tasks can be displayed at the same time. You can perform this operation to view the ancestor tasks that affect data output of the current auto triggered task.
Show Descendant Nodes: View the descendant tasks of an auto triggered task at different levels. A maximum of six levels of descendant tasks can be displayed at the same time. You can perform this operation to view the descendant tasks whose data output may be affected by the current auto triggered task.
View Code: View the code of an auto triggered task in the production environment. If the code of the auto triggered task does not meet expectations, you need to confirm whether the latest code of the task is successfully deployed to the production environment. For information about how to deploy a task to the production environment, see Deploy tasks.
Edit Node: Edit an auto triggered task on the configuration tab of the task on the DataStudio page.

Note

For information about other operations, see Perform operations on auto triggered tasks.

View the details of an auto triggered task

In the DAG of an auto triggered task, you can view the basic properties, detailed properties, operation log, and code of the task. This helps you check whether the scheduling parameters, resource group, and code of the task meet your business requirements.

In the DAG of an auto triggered task, click the task name. In the card that appears in the lower-right corner of the DAG, click Show Details. Then, view details of the auto triggered task on the tabs that appear.

Tab	Description
General	On this tab, you can view the scheduling properties of an auto triggered task in the production environment. For more information about the basic parameters, see Configure basic properties. Note If the parameter configurations for an auto triggered task on the DataStudio page are inconsistent with those for the task on the Auto Triggered Nodes page in Operation Center, we recommend that you check whether you successfully deploy the task after you modify the task. Rule Monitoring: You can view information about the alert rule that is associated with the auto triggered task. If no alert rule is associated with the auto triggered task, you can click Create on the right of the Rule Monitoring parameter to quickly create an alert rule to monitor the status of the task. For more information, see Create a custom alert rule. Note On the General tab, you can view the details of the alert rule that is used to monitor only the running status of an auto triggered task. You cannot view the data quality monitoring rule that is used to check data for an auto triggered task on the General tab. Baseline monitoring: You can view information about the baseline with which the auto triggered task is associated. If the value of the Baseline monitoring parameter is None, you can click Create to quickly create a baseline and associate the auto triggered task with the baseline. For more information, see Manage baselines. Note After you create a baseline and associate the auto triggered task with the baseline, the baseline is displayed as the value of the Baseline monitoring parameter on the General tab on the next day. To check whether the baseline is successfully created on the day when you configure the baseline, click Smart Baseline in the left-side navigation pane of the Operation Center page.
Operation Log	On this tab, you can view operation records of an auto triggered task, including the operation time, operator, and specific operations.
Code	On this tab, you can view the latest code of an auto triggered task in the production environment. If the code of the task does not meet expectations, you need to check whether the latest code of the task is successfully deployed to the production environment. For more information, see Deploy tasks.