DataWorks:View auto triggered instances

Intelligent search

If you use the intelligent search feature, you need to only enter the content that you want to query, Then, the system automatically parses and filters the instances that you want to query.

1. Perform the intelligent search operation.

   In the upper-right corner of the Instance Perspective tab of the Auto Triggered Instances page, click Intelligent Search. In the search box that appears, enter the content that you want to query, such as Sort by Instance Type, and press Enter. The system automatically matches and displays the instances that meet the specified condition.

2. Save the search condition as a new view.

   If you want to use the search condition that you specified in the future, you can perform the following operations to save the search condition as a new view: Choose Unsaved View > Save as New View under the search box. In the Save View dialog box, configure the View Name parameter and click Save. You can find and use the new view under the search box.

   Note

   If you do not want to use the new view in the future, you can perform the following operations to edit or delete the new view: Find the view under the search box. Move the pointer over the ... icon to the right of the view name andclick Edit or Delete based on your business requirements.

3. Disable the intelligent search feature.

   If you want to specify filter conditions to perform an exact search, you can press the Esc key or click Disable Intelligent Search to exit the intelligent search mode.

Condition-specific filtering

You can also specify filter conditions to perform an exact search.

1. Simple filtering:

   In the top toolbar of the Auto Triggered Instances page, you can specify a filter condition, such as task name, task ID, or instance ID entered in the search box, Scheduling Resource Group, Alerts Are Reported Within Last 24 Hours, or In Waiting for Resources State for a Long Period of Time to search for required instances.

2. Complex filtering:

   In the upper-right corner of the Auto Triggered Instances page, click Filter. In the pane that appears, you can specify multiple filter conditions, such as task name, task ID, or instance ID entered in the search box, Scheduling Resource Group, Scheduling Time, and Computing Resource Name to accurately search for required instances.

Manage an auto triggered instance

If you want to manage an auto triggered instance, find the instance in the instance list and click the feature button that you want to use in the Actions column. The following table describes the details of the features:

Manage multiple auto triggered instances at a time

If you want to perform operations on multiple auto triggered instances at a time, select the desired instances in the instance list and click Stop, Run, Set Status to Successful, Change Resource Group, Freeze, or Unfreeze at the bottom of the current page based on your business requirements.

Operations that you can perform on the DAG page

On the DAG details page of the instance, you can perform operations such as node aggregation, upstream and downstream analysis, and display pattern adjustment of the DAG.

DAG-related operations

On the DAG details page of the instance, you can right-click the instance name to view related information about the instance, such as the upstream and downstream dependencies and code details. The following information describes the operations that you can perform:

• Show Ancestor Nodes: You can perform this operation to view ancestor instances of the current auto triggered instance. You can select this option to have a command of the instances that affect data output of the current instance. You can view ancestor instances of an auto triggered instance by level. A maximum of six levels of ancestor instances can be displayed at the same time.

• Show Descendant Nodes: You can perform this operation to view descendant instances of the current auto triggered instance. You can select this option to have a command of the instances whose data output is affected by the current instance. You can view descendant instances of an auto triggered instance by level. A maximum of six levels of descendant instances can be displayed at the same time.

• View Runtime Log: After the auto triggered instance for which the test instance is generated is started, you can perform this operation to view the execution details of the auto triggered instance based on the operation logs. For more information about the core parameters in the logs, see Appendix: Parameters in operation logs.

• Instance Diagnose: You can perform this operation to check the instance from the following aspects: Upstream Nodes, Timing Check, Resources, and Execution.

• View Code: You can perform this operation to view the code of the task for which the current auto triggered 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.

• Edit Node: You can perform this operation to go to the configuration tab of the task for which the current auto triggered instance is generated on the DataStudio page.

• View Lineage: You can perform this operation to view the lineage of an auto triggered instance.

• More: You can view the basic properties, operations logs, and task code of an instance.

• View Auto Triggered Nodes: You can view the information of the auto triggered task to which the current instance belongs.

• Go to Task 360 Page: You can go to the Data Governance Center page to view the task running details from multiple perspectives, such as the baseline list and instance running status. Then, you can manage tasks. For more information, see Obtain a panoramic view of a task.

• Stop: You can perform this operation to stop an auto triggered instance that does not need to be run. After you perform this operation on an auto triggered instance, the auto triggered instance fails to be run and exits. Only auto triggered instances in the Pending (Schedule), Pending (Resources), or Running state can be stopped.

• Rerun: You can perform this operation to rerun an auto triggered instance that is in the Successful or Failed state. After the auto triggered instance is successfully run, its descendant instances that are in the Not Run state can be scheduled to run. This operation is used to process an auto triggered instance that fails to be run or an auto triggered instance that is not run as scheduled.

• Rerun Descendant Nodes: You can perform this operation to rerun the descendant instances of an auto triggered instance that is in the Successful or Failed state. You can select the descendant instance that you want to rerun. After the selected instance is successfully run, its descendant instances that are in the Not Run state can be scheduled to run. This operation is used to recover data.

• Set Status to Successful: You can perform this operation to set the status of an auto triggered instance that fails to be run to Successful. You can perform this operation if you do not want an auto triggered instance that fails to be run to block the running of its descendant instances. This operation is used to process an auto triggered instance that fails to be run.

• Resume: You can perform this operation to allow the current auto triggered instance to resume running from the position where it is stopped. For example, if an instance is run by executing multiple SQL statement segments, the instance resumes running from the SQL statement segment in which the SQL statements fail to be executed.

  Note

  Only SQL tasks that are run based on a MaxCompute compute engine support this operation.

• Trigger Data Quality Check: If auto triggered tasks are configured with data quality monitoring rules, the system checks the monitoring rule.

• Emergency Operations: You can perform emergency operations on the current auto triggered instance. The emergency operations take effect only on the current instance once.

  • Delete Dependencies: You can perform this operation to urgently delete dependencies for the current auto triggered instance. In most cases, you can delete dependencies for an auto triggered instance by clicking Delete Dependencies if the ancestor instances of the instance fail to be run and the ancestor instances do not affect data output of the instance.

    Note

    You must check whether this operation affects data output based on the code of the task for which the instance is generated and lineage of the instance.

  • Change Priority: You can perform this operation to change the priority of the auto triggered for which the current auto triggered instance is generated based on your business requirements. A larger value indicates a higher priority. The priority of a task depends on the priority of the baseline with which the task is associated.

  • Force Rerun: You can perform this operation to forcefully rerun the current auto triggered instance. You can perform this operation on an auto triggered instance that is in the Successful, Failed, or Not Run state. This operation is often performed to recover data.

  • Force Heavy Run Downstream: You can perform this operation to forcefully rerun the descendant instances of an auto triggered instance whose data timestamp is the previous day or the day before the previous day. You can perform this operation on an auto triggered instance that is in the Successful or Failed state. This operation is often performed to recover data. For more information, see Appendix: Forcefully rerun the descendant instances of an auto triggered node instance.

    Note

    You can use only a RAM user to which a workspace administrator or tenant administrator role is assigned, or an Alibaba Cloud account to forcefully rerun the descendant instances of an auto triggered instance.

  • Clone Instance: You can click Clone Instance to create a new instance with the same configurations as a host instance that is in the Running state. The new instance is a cloning instance. The new instance is named in the dw_clone_Node name format.

    Note

    • You can clone only instances generated based on ODPS SQL nodes. Each instance can be cloned only once.

    • Execution logic of the host instance and the cloned instance:

      • Both the host instance and the cloned instance are in the Running state. If the host instance succeeds before the cloned instance, the cloned instance will be stopped. If the cloned instance succeeds before the host instance, the host instance will be stopped and enter the Successful state.

      • If a cloned instance exists in a downstream task of the current task, the cloned instance is not rerun when you rerun the descendant instances of the host instance.

• Freeze: You can perform this operation if you do not need to run an auto triggered instance and its descendant instances.

  Important

  • After an auto triggered instance is frozen, its descendant instances cannot be scheduled and run as expected. Proceed with caution.

  • Do not perform this operation on 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.

  • You cannot freeze an auto triggered that is in one of the following states: Pending (Resources), Pending (Schedule), and Running. If the code of the task is being executed or data quality of the task is being checked, the status of the task can be considered running.

• Unfreeze: You can perform this operation to unfreeze an auto triggered instance that is frozen.

  • If the auto triggered instance is not run, it is automatically run after its ancestor instances are successfully run.

  • If all the ancestor instances of the auto triggered instance are successfully run, the state of the auto triggered instance is directly set to Failed. You must manually rerun the auto triggered instance.

  Note

  The unfreeze operation takes effect only on the current auto triggered instance. If the auto triggered for which the instance is generated is frozen, instances that are scheduled to run on the next day are also frozen.

View the details of the auto triggered instance

On the DAG details page of the instance, right-click the instance and select View Runtime Log or More to check the property, runtime log, operation log and code details of the instance.