Auto triggered instances

Intelligent search mode

With intelligent search, you can simply enter a query, and the system automatically parses it to filter for the required instances.

1. Perform an intelligent search.

   Click the Intelligent Search button in the filter box. In the dialog box that appears, enter your search query, such as Sort by instance type, and press Enter. The system automatically displays matching instances.

2. Save a new view.

   If you need to reuse the search criteria from your intelligent search, you can click Unsaved View > Save as New View in the search bar. In the Save View dialog box, enter a custom View Name and click Save. You can then find and use this new view from the view search bar.

   Note

   If you no longer want to use this view, find its name in the view search bar. Hover over the view name, click the ... icon on the right, and select Modify or Delete.

3. Disable intelligent search.

   If you need to perform a precise search using filter conditions, you can press the Esc key or click the Disable Intelligent Search button in the instance actions bar to exit the intelligent search mode.

Filter conditions mode

Use filter conditions to precisely find the auto triggered instances you need.

1. Simple filtering.

   In the toolbar, you can select multiple filter criteria, such as Search by task name, task ID, or instance ID, Scheduling Resource Group, Alerts Reported Within Last 24 Hours, or In Waiting for Resources State for a Long Period of Time, to filter instances.

2. Advanced filtering.

   Click the Filter button in the filter box. You can then combine multiple criteria, such as Search by task name, task ID, or instance ID, Scheduling Resource Group, Run time, and Computing Resource Name, to accurately find the required instances.

Sorting mode

You can sort the auto triggered instance list in ascending or descending order by fields such as Data Timestamp, Priority, and Timing Time. For workflows that have run successfully, you can sort the internal tasks by Start Time, End Time, and Duration.

Manage a single instance

To manage a specific auto triggered instance, find it in the list and use the actions in the Actions column. The following table describes the available actions.

Manage multiple instances

To manage multiple auto triggered instances at once, select the instances in the list. Then, use the bulk operation buttons at the bottom of the list to Terminate, Rerun, Set to Successful, Change Resource Group, Freeze, or Unfreeze them.

To export the list of instances from your search results, first perform a search. Then, click the Export Query Results button above the instance list. In the Export Query Results dialog box, confirm the following information:

• Operation Object: Displays the number of instances matching the current filter criteria. You can click View Filter Conditions to see the specific filters.

• Export Method: Select Export to Local File.

DAG page features

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

DAG actions

On the DAG details page, right-click an instance in the workflow to view details such as its upstream and downstream relationships and code. The following actions are available:

• Show Ancestor Nodes: View the upstream tasks of the current node to understand which nodes affect its data output. You can expand ancestor nodes by level, up to six levels at a time.

• Show Descendent Nodes: View the downstream tasks of the current node to understand which nodes are affected by its data output. You can expand descendant nodes by level, up to six levels at a time.

• View Runtime Log: After a task starts, you can view its detailed execution process in the runtime log. For descriptions of the core parameters in the log, see Appendix: Runtime log parameters.

• Run Diagnostics: Checks the task's upstream dependencies, scheduling time, scheduling resources, and running status.

• View Code: View the code of the current node in the production environment. If it is not as expected, verify that the latest version of the node has been successfully deployed.

• Edit Node: Opens the current node in DataStudio.

• View Lineage: View the data lineage of the current instance.

• More: View details such as the instance's basic properties, operation logs, and task code.

• View auto triggered node: View information about the auto triggered node to which the current instance belongs.

• Go to task 360 page: Go to the Data Governance Center to get a panoramic view of task details from multiple dimensions, such as associated baselines and instance run status, and perform task governance. For more information, see Get a panoramic view of a task.

• Terminate: Stops a task that you no longer need to run. The task status will be set to failed. You can only stop instances that are in the Waiting time, Waiting for resources, or Running state.

• Rerun: Reruns a task that is in a Successful or Failed state. After the task runs successfully, it can trigger its un-run downstream tasks. This is often used to handle failed or missed nodes.

• Rerun Descendent Nodes: Reruns the descendant nodes of a task that is in a Successful or Failed state. You can select which downstream tasks to rerun. After they run successfully, they can trigger their un-run downstream tasks. This is often used for data recovery.

• Set to Successful: Sets the status of a failed task to successful. This is useful when you do not want a failed task to block its downstream tasks. This is often used to handle failed nodes.

• Resume: Resumes a failed task from the point of failure. If a task contains multiple SQL statements, it can resume from the specific SQL statement that failed.

  Note

  This operation is supported only for MaxCompute SQL tasks.

• Trigger Data Quality Check: If data quality rules are configured for the task, you can trigger a validation check.

• Emergency Operations: Emergency operations are single-use and affect only the current run of the node.

  • Delete Dependencies: Removes the dependency relationships for the current node. This is often used to urgently remove an upstream dependency when an upstream task fails but is not related to the data of the current instance, allowing the current task to run.

    Note

    You must confirm whether this action will affect your data by checking the task code and data lineage.

  • Change Priority: The priority of an instance is inherited from its baseline. You can reset the priority here as needed. A higher number indicates a higher priority.

  • Force Rerun: Forces a rerun of the current node. This can be done on auto triggered instances that are in successful, failed, or not-run states. This is often used for data recovery.

  • Force Heavy Run Downstream: Forcefully reruns downstream tasks to process data for the two preceding business dates. This operation is supported only for auto triggered instances in a Successful or Failed state and is often used for data recovery. For more information, see Appendix: Force rerun downstream.

    Note

    Only workspace administrators, tenant administrators, and Alibaba Cloud accounts can initiate a force rerun of downstream nodes.

  • Clone Instance: Creates a new clone instance based on a running instance (the host instance). The new instance is named in the format dw_clone_NodeName.

    Note

    • Only ODPS SQL node instances can be cloned, and each instance can be cloned only once.

    • Execution logic for host and clone instances:

      • Both the host and clone instances are in the running state. If the host instance succeeds first, the clone instance is stopped. If the clone instance succeeds first, the host instance is stopped and its status is set to successful.

      • If a downstream task of the current task has a clone instance, rerunning the downstream nodes will not trigger the execution of the clone instance.

• Freeze: You can freeze an instance if it and its downstream instances do not need to run.

  Important

  • Freezing an upstream instance blocks its downstream instances from running. Proceed with caution.

  • Do not operate on the projectname_root node, as it is the root node of the workspace. All auto triggered instances depend on this node. If you freeze this node, no auto triggered instances will run.

  • You cannot freeze an instance that is in the Waiting for resources, Waiting time, or Running state (for example, if the node code is running or a data quality check is in progress).

• Unfreeze: Unfreezes an instance that is in a frozen state.

  • If the instance has not yet run, it will run automatically after its upstream tasks are complete.

  • If all upstream tasks have already completed, the instance's status changes to failed. You must then manually rerun it.

  Note

  The unfreeze operation affects only the current instance. If the auto triggered node is still frozen, the instance generated the next day will also be frozen.

Instance details

In the instance DAG, left-click a specific instance and click View Log Data in the pop-up window, or click Show Details to view detailed information such as General, Runtime Log, Operation Log, and Code.