DataWorks:View auto-triggered instances

Intelligent search mode

The intelligent search feature automatically parses your query to quickly filter and display the required instances.

1. Perform an intelligent search.

   Click the Intelligent Search button in the filter bar. In the dialog box that appears, enter your search content, such as sort by instance type, and press Enter. The system will automatically find and display the matching instances.

2. Save a new view.

   To reuse the search conditions from your intelligent search, 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 in the view search bar for future instance searches.

   Note

   If you no longer need the new view, find it in the view search bar. Hover over the view name, click the ... button on the right, and select Modify or Delete.

3. Disable intelligent search.

   To perform a precise search using filter conditions, press the Esc key or click the Disable Intelligent Search button in the instance toolbar to exit the intelligent search mode.

Filter mode

The filter feature allows you to precisely narrow down the instance list based on specific criteria.

1. Simple filtering.

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

2. Advanced filtering.

   Click the Filter button in the filter bar to combine multiple conditions, such as Search by task name, task ID, or instance ID, Scheduling Resource Group, Scheduling Time, and Computing Resource Name, to accurately locate the required instances.

Sort mode

You can sort the instance list by custom fields in ascending or descending order, such as by Business Date, Priority, or Scheduled Time. For successfully executed workflows, you can sort internal tasks by Start Time, End Time, or Duration.

Manage a single instance

To manage an Auto Triggered Instance, locate it in the instance list and use the options in the Actions column. The following table describes the available actions.

Manage multiple instances in batches

To perform batch operations, select multiple Auto Triggered Instances from the list and use the buttons at the bottom to perform actions such as Stop, Rerun, Set status to successful, Change resource group, Freeze, and Unfreeze.

To export the instance list from your search results, first apply your filters, and then click the Export Query Results button above the instance list. In the Export Query Results dialog box, confirm the following information:

• Objects: 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.

DAG panel features

On the instance DAG details page, you can use the following features in the DAG panel to aggregate nodes, analyze downstream dependencies, and adjust the DAG display style.

DAG operations

On the instance DAG details page, right-click an instance in the workflow to view its dependencies, code details, and other information. The following operations are available:

• Show Ancestor Nodes: View the upstream tasks of the current node to understand which nodes affect its data output. You can expand up to six levels of parent nodes 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 up to six levels of child nodes at a time.

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

• Instance Diagnose: Performs diagnostic checks on the task's upstream dependencies, scheduling time, scheduling resources, and running status.

• View Code: Confirms 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 published.

• Edit Node: Opens the current node in the DataStudio page.

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

• More: View the instance's basic properties, operation log, task code, and other information.

• View Auto Triggered nodes: View information about the Auto Triggered Task to which the current instance belongs.

• Go to Task 360 page: Navigates to the Data Governance Center to get a panoramic view of the task's details from multiple dimensions, such as associated baselines and instance execution status, for governance purposes. For more information, see Get a panoramic view of a task.

• Stop: Terminates a task that should no longer run. The task will exit with a failed status. You can only stop instances that are in the Pending (Schedule), Pending (Resources), or Running state.

• Rerun: Reruns a task that is in the Successful or Failed state. A successful execution can trigger the scheduling of unexecuted downstream tasks. This is often used to handle failed or missed nodes.

• Rerun Descendent Nodes: Reruns the downstream nodes of a task that is in the Successful or Failed state. You can select which downstream tasks to rerun. A successful execution triggers the scheduling of unexecuted downstream tasks. This is typically used for data backfilling.

• Set status to successful: Sets the status of a failed task to successful. Use this when a task has failed but you do not want it to block downstream tasks. This is often used to handle failed nodes.

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

  Note

  This operation is supported only for MaxCompute SQL tasks.

• Trigger Data Quality Check: If the task is configured with data quality rules, this triggers a check against those rules.

• Emergency Operations: These operations are effective only for the current run of this node.

  • Delete Dependencies: Removes dependencies for the specified task, allowing the current node to run. This is often used to bypass an upstream failure that does not have a data relationship with the current instance.

    Note

    Verify whether this operation 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 it here as needed. A higher number indicates a higher priority.

  • Force Rerun: Forces the current node to rerun. This can be performed on an Auto Triggered Instance that is successful, failed, or has not run. It is commonly used for data backfilling.

  • Force Heavy Run Downstream: Used to reprocess data from the previous or second-to-previous business date. This can only be performed on a successful or failed Auto Triggered Instance and is commonly used for data backfilling. For more information, see Appendix: Forcefully rerun descendant nodes.

    Note

    Only workspace administrators, tenant administrators, or the primary Alibaba Cloud account can initiate a forced rerun of downstream nodes.

  • Clone Instance: Creates a new instance (clone) with the same configuration as the current Running instance (host). 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 will not trigger the clone instance.

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

  Important

  • Freezing an upstream instance blocks the execution of its downstream instances. Use this operation 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 it. Freezing this node will prevent all Auto Triggered Instances from running.

  • You cannot freeze instances that are in the Pending (Resources), Pending (Schedule), or Running state (for example, when node code is running or a data quality check is in progress).

• Unfreeze: Unfreezes an instance.

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

  • If all upstream tasks are already complete, the instance will be set to failed and must be manually rerun to execute properly.

  Note

  The unfreeze operation only affects the current instance. If the parent Auto Triggered Task is still frozen, the instance generated the next day will also be frozen.

View instance details

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