View and manage auto triggered tasks - DataWorks - Alibaba Cloud ドキュメントセンター

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 the current 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

For information about how to create, deploy, run, or undeploy an auto triggered task, or suspend the scheduling of an auto triggered task, see Perform basic O&M operations on auto triggered tasks.
DataWorks automatically generates auto triggered instances that are scheduled to run on the next day for an auto triggered task every night. An auto triggered task can be manually triggered to enable the system to generate a data backfill instance or a test instance for the task. You can obtain the running details of the auto triggered task by viewing the generated instance.

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 projectname_root task, which is the root task of your workspace. All the 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. You may encounter the following unexpected situations 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 Governance > 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 the list of auto triggered tasks

On the Auto Triggered Nodes page, you can view the list of auto triggered tasks that you commit to the scheduling system and perform O&M operations on the tasks. 周期任务列表

Operation item	Description
Filter	In the area marked with 1 in the preceding figure, you can specify conditions to search for your desired auto triggered task. You can search for your desired auto triggered task by task name or task ID. You can also specify the following conditions to search for your desired auto triggered task: Node Type, Owner, Scheduling Resource Group, Region, Solution, Label, Workflow, Data Source Type, Data Source Name, Baseline, Priority, Scheduling Cycle, and Workflow. 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.
List of auto triggered tasks	In the area marked with 2 in the preceding figure, you can view the auto triggered tasks that meet the specified conditions.
Operations on a single task	In the area marked with 3 in the preceding figure, you can perform operations on an auto triggered task. DAG: You can perform this operation to view the dependencies of an auto triggered task. On the DAG page, you can right-click the task in the DAG to perform related operations. For more information, see View the DAG of an auto triggered task. Test: You can perform this operation 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: You can perform this operation 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: You can perform this operation if an auto triggered task and its descendant nodes do not need to be run for a period of time. Note Do not freeze the projectname_root task, which is the root task of your workspace. All the instances of auto triggered tasks depend on this task. If this task is frozen, the instances of auto triggered tasks cannot be run. Unfreeze: You can perform this operation to unfreeze an auto triggered task that is frozen. Change Owner: You can perform this operation to change the owner of an auto triggered task. Modify Scheduling Resource Group: You can perform this operation to change the resource group for scheduling that is used to run an auto triggered task to another resource group for scheduling. Modify label: You can perform this operation 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: You can perform this operation to configure a data quality monitoring rule to check data for an auto triggered task during the running of the task. For more information, see Overview. View Instances: You can perform this operation to view instances generated for an auto triggered task on the Auto Triggered Instances page. View Lineage: You can perform this operation to view data lineage of an auto triggered task. View cycle task details: You can perform this operation 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: You can perform this operation 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: You can perform this operation to associate an auto triggered task with a baseline. For information about baselines, see Overview.
Batch operations	In the area marked with 4 in the preceding figure, you can perform an operation on multiple auto triggered tasks at a time. You can select multiple auto triggered tasks and click the following buttons to perform operations on the tasks at a time: Freeze, Unfreeze, Change Owner, and Modify Scheduling Resource Group. You can also select multiple auto triggered tasks, click Actions, and then select an option from the shortcut menu to perform the corresponding operation on the tasks at a time.
Items per page	In the area marked with 5 in the preceding figure, you can select the number of items that you want to view on a single page. The maximum number that you can select is 200.

View the DAG of an auto triggered task

In the list of auto triggered tasks, click the name of an auto triggered task in the Name column or click DAG in the Actions column of the task. On the DAG page, the system automatically displays the level-1 ancestor tasks and level-1 descendant tasks of the task. You can view the other ancestor and descendant tasks of the current task by clicking the icons for the node aggregation and descendant task analysis features in the upper-left corner of the DAG page. You can also right-click the task to perform related operations. 周期任务

Functionality	Description
Operations that you can perform on the DAG page	You can use the task aggregation and descendant task analysis features and adjust the display style of the DAG of a task by clicking icons in the areas marked with 1 in the preceding figure. For more information, see Appendix: Use the features provided in a DAG. Task aggregation: You can use this feature to aggregate tasks from different dimensions such as task status, workspace, owner, or priority. Descendant task analysis: 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 this feature to calculate the number of descendant tasks that are affected by the current task. Adjust the display style of the DAG: You can adjust the display style of the DAG of a task by clicking the icons in the upper-right corner of the DAG page.
Operations on a single node	You can perform related operations on an auto triggered task in the DAG of the task by selecting options in the area marked with 2 in the preceding figure. Show Ancestor Nodes: allows you to 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 task. Show Descendant Nodes: allows you to view 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 is affected by the current task. View Code: allows you to view the code of an auto triggered task in the production environment. If the code of the task does not meet expectations, you need to confirm whether the latest code of the task is successfully deployed to the production environment. For more information about how to deploy a task to the production environment, see Deploy tasks. Edit Node: allows you to edit an auto triggered task on the configuration tab of the task on the DataStudio page. Note For information about other operations, see View the list of auto triggered tasks.
Details about a single task	You can view the basic properties of an auto triggered task in the area marked with 3 in the preceding figure. You can also click Show Details in this area to view the detailed properties, context parameters, operation logs, and code of the task. For more information, see View the details of an auto triggered task.

View the details of an auto triggered task

After you click Show Details in the lower-right corner of the DAG page of an auto triggered task, multiple tabs appear. On these tabs, you can view various properties of the auto triggered task in the production environment and check whether the code of the task meets your expectations. The properties include scheduling parameters and the resource group that are configured for the auto triggered task.

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 Tasks page in Operation Center, we recommend that you check whether you successfully deploy the task after you modify the task. Rule-based monitoring: You can view information about the alert rule that is associated with the task. If no alert rule is associated with the 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 You can view only the details of the alert rule that is used to monitor the status of an auto triggered task on the General tab. 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 task is associated. If the task is not associated with baselines, you can click Create on the right of the Baseline monitoring parameter to quickly create a baseline. For more information, see Manage baselines. Note After you create and configure a baseline, the baseline is available to choose as an option on the Auto Triggered Nodes page 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.
Context Parameters	In this section, you can view the input parameters and output parameters of an auto triggered task. For more information, see Configure input and output parameters.
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 confirm whether the latest code of the task is successfully deployed to the production environment. For more information, see Deploy tasks.