, - Dataphin - Alibaba Cloud Documentation Center

Recurring instances are automatically generated when recurring tasks run on schedule, based on their scheduling configurations. Each scheduled recurring task generates an instance. You can manage these generated instances by checking their running status, rerunning them, or viewing their node code. This topic describes the general features of recurring instances.

Recurring Instance Generation Time and Running Rules

Dataphin generates recurring instances for the next day at 23:00 nightly. By default, generated instances are in the Not Running state.

After all ancestor instances on which a recurring instance depends have run successfully, the recurring instance's status changes from Not Running to Waiting for Scheduled Time.
When the current instance's scheduled running time arrives, and Dataphin has sufficient available schedule resources and passes all applicable throttling rules, the recurring instance's status changes from Waiting for Scheduled Time to Running.
Note
Pausing a recurring instance pauses the execution of the current recurring instance. It does not affect the execution of other recurring instances generated by this node. To pause the execution of multiple recurring instances, you can modify the schedule property of this node to skip execution. For more information, see Manage integration and compute nodes.

Recurring Instance Page Entry

On the Dataphin home page, in the top menu bar, select Development > Task O&M.
In the top menu bar, select the production or development environment.
In the navigation pane on the left, select Instance O&M > Recurring Instances.

Recurring Instances Page Introduction

The Recurring Instances page primarily displays the Integration and Compute Tasks list and the Modelling Task list. On this page, you can perform O&M operations on submitted recurring instances.

Block	Description
①Search and Filter Area	Filter: Select My Instances, Failed Instances, Unfinished Instances, and choose a data timestamp and project for quick filtering. The following filter options are also supported: My Instances: All instances for which the current logged-on account is responsible. Failed Instances: All failed instances in projects where the current logged-on user has the O&M - Access Directory permission. Unfinished Instances: All unfinished instances in projects where the current logged-on user has the O&M - Access Directory permission. Project: Filter by the project where the task resides. Select multiple projects where the current logged-on user has the O&M - Access Directory permission. Data Timestamp: Select Today, Yesterday, All, or a specific day or data timestamp range. Instance Type: Select Integration and Compute Tasks type or Modelling Task type. Subtype: The supported subtypes vary based on the selected business type, as follows: Integration and Compute Tasks type: The supported subtypes vary based on the bound compute engine type. Refer to the page display for details. Modelling Task type: Supports logical dimension table, logical fact table, and logical aggregate table. Operation Owner: Filter by the instance O&M owner. Operational Status: Supports the following seven operational statuses: Passed, Failed, Running, Waiting for scheduled time, Rate limiting, Waiting for scheduling resources, and Not run. For information about the identifiers and details of each status, see Recurring instance operational status description. Priority: Filter by 5 instance running priorities: Highest, High, Medium, Low, and Lowest. Note If the baseline feature is enabled, task priorities only support Medium, Low, and Lowest. Recurrence: Select multiple scheduling cycles to filter by. Supports 6 scheduling cycles: Minute, Hour, Day, Week, Month, and Year. Running Mode: Filter by the instance's running mode. Running modes include Normal Run, Dry Run, and Paused Run. Start Running Time: Filter by the recurring instance's start running time. Select Last Hour, Today, Yesterday, or a specific day or business time range (accurate to seconds). Non-Scheduled Day Instances: These are dry-run instances generated by the system on non-scheduled days. This does not include configured dry-run instances (does not include dry-runs configured by conditional scheduling). Supports Show or Hide. Note For logical table instances, they are hidden only when all fields are dry-run on non-scheduled days. End Time: Filter by the instance's end running time. Select Last Hour, Today, Yesterday, or a specific day or business time range (accurate to seconds). Scheduled Time: Filter by the recurring instance's scheduled running time. Select 0–6 o'clock, 6–12 o'clock, 12–18 o'clock, or a specific time range (accurate to seconds). Running Duration: Filter by the total time or range from instance start to end. Resource Group: Filter by the schedule resource group specified for the instance at runtime. Retry Count: Enter the retry count range in the format `a~b`. The default value for 'a' is 0, and the default value for 'b' is empty. If 'b' is empty, it means all values greater than 'a' are included. Both 'a' and 'b' can be 0 or positive integers. Note Modelling tasks do not support this filter option. Auto Retry Count: Enter the auto retry count range in the format `a~b`. The default value for 'a' is 0, and the default value for 'b' is empty. If 'b' is empty, it means all values greater than 'a' are included. Both 'a' and 'b' can be 0 or positive integers. Note Modelling tasks do not support this filter option. Tag: Select one or more task tag values to filter by. Click Reset to quickly clear all filter conditions and restore system defaults. Search: Search for recurring instances by entering a node ID or node name. You can also click the icon in the search box to open the Batch Search dialog box. In the Batch Search dialog box, manually enter multiple task IDs or upload a document to search. Batch search can also be combined with other filter conditions. Batch Search - Manual Input: In the Batch Search dialog box, select Manual Input. Enter up to 5000 task IDs, separated by line breaks. After entering, click Confirm to search. Batch Search - Upload Document: In the Batch Search dialog box, select File. Click Upload to upload an Excel file. The system automatically reads the first column (task ID column) and rows 2-5001 from the first sheet of the Excel file. Click Download Task ID List Template to edit using the template.
②List Operations	Customize List Table Header: Click the icon to select list display items and adjust their display order. Note The first column and the operation column do not support canceling display or adjusting order. After clearing browser cache or changing browsers, the table header restores to default settings. Refresh List: Click the icon to refresh the current list.
③Recurring Instance List	The Recurring Instances page displays all recurring tasks in projects where the current user has the O&M - Access Directory permission, in a list format. These tasks are categorized into Integration and Compute Tasks and Modelling Task. The Actions column shows the O&M management operations supported for recurring instances. Details of O&M operations supported by each recurring instance type are as follows: For the O&M operations supported for the list of integration and computation task instances, see Operations supported for the list of integration and computation task instances. For more information about O&M operations supported by modeling task instances, see Operations supported by periodic modeling task instances. Note The recurring instance list only displays instances of the current tenant.
④Batch Operations	Use the batch operations area to rerun, stop, set to successful and continue scheduling, pause, resume, modify schedule resource groups, and modify priority for recurring instances. This improves operational efficiency. For more information about batch operations supported by Integration and Computing task instances, see Integration and Computing Task Instance Batch Operations For the batch operations supported for modeling task instances, see Logical Table Fields and Batch Operations.
④Time Zone Conversion	If the tenant's scheduling time zone and the system time zone (displayed in the User Center) are inconsistent, use time zone conversion to view the Scheduled Running Time, Start Running Time, and End Running Time under either the scheduling time zone or the system time zone. Note The start running time, end time, and scheduled time in the filter only support filtering by the system time zone.

Recurring Instance Hint Mark Description

Mark	Hint	Description
	Data Latency	For event logical fact tables with data latency enabled, this mark appears when Dataphin detects data latency after the recurring instance runs successfully.
	Dry Run	The scheduling property of this recurring instance task is set to dry run scheduling.
	Paused	The scheduling property of this recurring instance task is set to skip execution.

Recurring Instance Running Status Description

Status Mark	Running Status	Description
	Not Running	Instances that have not started running.
	Waiting for Schedule Resources	All dependent ancestor nodes have run successfully, waiting for schedule resources.
	Throttling	Instances currently being throttled.
	Waiting for Scheduled Time	All dependent ancestor nodes have run successfully, waiting for the scheduled time to arrive.
	Running	Instances currently running.
	Failed	Instances that failed to run. If you stop an instance in the waiting or running state, its status changes to failed.
	Success	Instances that ran successfully. The system directly marks dry-run scheduled instances as successful.

Recurring Instance DAG Graph

Click the instance object name in the recurring instance operations list. The page on the right displays a DAG graph centered on the current node. The DAG graph dynamically visualizes the ancestor and descendant dependencies of the node. By default, it shows the Main node (selected node) and the first layer of ancestor and descendant nodes. If a real-time instance has no ancestor or descendant nodes, the DAG graph only displays the current Main node. The system also supports O&M and management of ancestor and descendant nodes.

You can adjust the DAG graph page range as follows:

Click the icon to hide the real-time instance list and enlarge the DAG graph.
Click the icon to hide the DAG graph.
Hover the mouse pointer over the icon and drag to expand or shrink the DAG graph's page range.

The DAG graph interface information for Modelling Task instances is the same as for Integration and Compute Task instances. The following figure uses an Integration and Compute Task instance as an example:

Section	Description
①Node Information	Displays summary information for the currently selected node. Click View Node Details to see more node information, including instance probability, running diagnosis, operational log, operation log, node code, and task parameters. Instance Overview: Displays basic information (such as the current node's name, ID, instance ID, tenant, and project), running information (such as running status and running time), and resource consumption (memory/CPU allocation, actual memory/CPU consumption). Note Except for SQL tasks (compute engine SQL tasks and database SQL tasks), resource consumption information is displayed in the node details of recurring instances and data backfill instances only when System Settings > Resource Settings > Schedule Resource Dashboard is enabled under the metadata warehouse tenant. External tenant nodes (nodes not belonging to the current tenant) do not support viewing Gantt charts or running diagnosis. Run Diagnosis: View the upstream dependencies, scheduled time, throttling rules, scheduling resources, and execution of the current instance. For more information, see Instance Run Diagnosis. Operational Log: View the operational log for the current instance's successful or failed runs. Operation Log: View the operation log for the current instance, including operation time, operator, and specific operation. Node Code/Materialization Code: View the code for the current instance. Integration and Compute Task Instances: Includes instance overview, running diagnosis, operational log, operation log, and node code. Modelling Task Instances: Includes instance overview, running diagnosis, operational log, operation log, and materialization code. External Tenant Nodes (nodes not belonging to the current tenant): Only display the instance overview.
②Node Filter Area	Quickly set the expansion level up and down from the Main node. If many nodes are expanded and difficult to view, search for a node name to quickly locate a specific node within the current DAG graph display range.
③Schedule Dependency Graph	Displays the instance's schedule dependency graph. Expand more nodes up and down, and perform O&M operations on ancestor and descendant nodes. Hover the mouse pointer over a DAG node to view its name, type, scheduling cycle, O&M owner, and description. If a node has ancestor or descendant nodes not belonging to the current tenant, the external tenant node displays a cross-tenant tag and only supports expanding its parent node and child node. For O&M operations supported by periodic integration and computing instance DAG nodes, see O&M operations supported by integration and computing task instance DAG nodes. For the O&M operations supported by periodic modeling task DAG nodes, see Operations supported by modeling task instance DAG nodes.
④Canvas Adjustment Area	Quickly adjust the DAG display ratio. This includes setting the display ratio (default is 100%), enlarging based on the current ratio (maximum 200%), shrinking based on the current ratio (minimum 20%), fitting to canvas, and full-screen display. It also shows the node ID and node name of the Main node in the current DAG graph.
⑤Instance Object List	When viewing the DAG graph, the instance object list displays the instance object's name and data timestamp. Hover the mouse pointer over an instance object to view its node name, node ID, scheduling cycle, data timestamp, and scheduled running time. See the following figure: