how to use the recurring task feature - Dataphin - Alibaba Cloud Documentation Center

Recurring tasks are tasks that run automatically based on a defined schedule. This topic describes the common features of recurring integration, computing, and modeling tasks. Modeling tasks include logical dimension tables, logical fact tables, and logical aggregate tables. This topic also explains their usage, supported scheduling types, and related features.

Usage instructions

The Operation Center supports automatic scheduling for recurring instances in the production environment. In the development environment, the Operation Center generates recurring instances but does not automatically schedule them.

Access the recurring task page

In the top menu bar of the Dataphin home page, choose Development > Task Operations.
In the navigation pane on the left, choose Task Operations > Recurring Task.
In the top menu bar, select the production or development environment.

Introduction to the recurring task page

The recurring task page displays the Integration and Computing Tasks list and the Modeling Task list. You can perform related operations on the corresponding tabs.

Section	Description
① Filter and search area	Enter a node ID or task object name to filter recurring tasks. You can also select My Tasks, Paused Tasks, or Dry-run Scheduling Tasks for quick filtering. My Tasks: Tasks that belong to the current logon account. Paused Tasks: Tasks in the current project whose scheduling property is set to pause scheduling. Dry-run Scheduling Tasks: Tasks in the current project whose scheduling property is set to dry-run. Click Filter to expand the filter area for more options. The supported filter items include the following: Task Type: Data_disitll projects support script tasks. Non-Data_disitll projects support Integration And Computing Tasks and Modeling Task. Integration And Computing Tasks: The supported script tasks vary by compute engine. The actual options are displayed on the page. Modeling Task: Includes logical dimension tables, logical fact tables, and logical aggregate tables. Scheduling Mode: Filter by normal scheduling, dry-run scheduling, or paused scheduling. For more information, see Scheduling mode description. Priority: Filter by instance run priority. Options are Highest, High, Medium, Low, and Lowest. Note If the baseline feature is enabled, only Medium, Low, and Lowest task priorities are supported. Project: Filter by project. You can select multiple projects for which the current logon user has Operations - Access directory permissions. Operation Owner: Filter by the owner of the recurring task. Recurrence: Filter by scheduling cycle. Options are Minute, Hour, Day, Week, Month, and Year. Update Time: Filter by the date or date range when the recurring tasks were updated. Resource Group: Filter by the scheduling resource group configured for the recurring tasks. Note This filter is supported only for integration and computing tasks. To filter again, click Reset to clear all filter conditions and restore the defaults.
② Recurring task list area	The recurring task page lists all recurring tasks in projects for which the current user has Operations - Access directory permissions. The tasks are categorized into Integration And Computing Tasks and Modeling Task. The Actions column shows the supported operations for each task. For details about the supported operations for each task type, see the following documents: For more information about operations supported in the integration and computing task list, see Operations supported in the integration and computing task list. For more information about operations supported in the modeling task list, see Operations supported in the modeling task list.
③ Batch operations area	Use the features in the batch operations area to process recurring tasks in batches and improve efficiency. For more information about batch operations supported for integration and computing tasks, see Batch operations supported for integration and computing tasks. For more information about batch operations supported for modeling tasks, see Batch operations supported for modeling tasks.

Scheduling mode description

Icon	Scheduling status	Description
None	Normal scheduling	The task runs normally according to the configured scheduling cycle and start time.
	Dry-run scheduling	The task is scheduled according to the time configuration, but it runs in dry-run mode. This means the task immediately returns a success status without actually running.
	Pause scheduling	Instances generated for tasks with paused scheduling are in the Paused state. Use the Resume operation to resume the instances. Pausing is suitable for scenarios where some tasks and their downstream nodes do not need to run temporarily but will be used later. For example, you can temporarily adjust calculation logic to prevent affecting downstream data. Note the following details: After a task is paused, instances are generated normally at midnight every day. All generated instances are in the Paused state. Pausing a task is suitable for scenarios where the task node and its downstream nodes do not need to be scheduled, but the task does not need to be unpublished. After a task is resumed, its scheduling mode changes from paused scheduling to normal scheduling. For a paused task, if some instances need to run, you can manually restore the instances to the normal scheduling state.

DAG of recurring tasks

Click a task object name in the list to show its Directed Acyclic Graph (DAG) on the right. The DAG visualizes the upstream and downstream dependencies of the node. By default, the DAG shows the main node (the selected node) and its first-level upstream and downstream nodes. If a task has no dependencies, the DAG shows only the main node. You can also manage the upstream and downstream nodes on the graph.

You can also adjust the DAG view:

Click the icon to hide the real-time instance list and enlarge the DAG.
Click the icon to hide the DAG.
Hover over the icon and drag to expand or shrink the DAG canvas.

The following figure shows an example of a recurring script task:

Section	Description
① Node information	Displays a summary of the selected node. Click View Node Details to see more information. Task overview: Displays basic information about the node, such as its name, ID, type, and project or data domain. Operation logs: Displays the time, operator, and operation. Node code/Materialization code: Displays the node's code. You can view all versions of the node in the production environment. Click the icon to compare versions. Click the icon to view version information, including the creation time and the user who made the modification. Task parameters: Displays the parameters for the node task. Integration and computing task nodes: Include task overview, operation logs, and node code. Modeling task nodes: Include task overview, operation logs, and materialization code. Real-time tasks: Include node details, operation logs, node code, and task parameters.
② Node filter area	Quickly set the number of upstream and downstream levels to expand from the main node. If many nodes are expanded, search for a node ID or name to quickly locate a specific node within the current DAG view.
③ Scheduling dependency graph	Displays the scheduling dependency graph for the instance. You can expand more upstream and downstream nodes and perform operations on them. Hover your mouse over a node in the DAG to view its name, type, scheduling type, owner, and description. For more information about operations supported for DAG nodes of integration and computing tasks, see Operations supported for DAG nodes of integration and computing tasks. For more information about operations supported for DAG nodes of modeling tasks, see Operations supported for DAG nodes of modeling tasks.
④ Canvas adjustment area	Quickly adjust the DAG display scale. You can set a specific scale (default is 100%), zoom in (up to 200%), zoom out (down to 20%), fit to canvas, or display in full screen. This area also shows the node ID and name of the main node in the current DAG.