Offline scheduling templates

Permission requirements

Only super administrators, system administrators, and custom global roles with the Common Business Logic-Management permission point can create and manage offline scheduling templates.

Create an offline scheduling template

1. In the top navigation bar of the Dataphin homepage, choose Planning > Common Business Logic.

2. On the Common Business Logic page, click the Offline Scheduling Templates tab.

3. On the Offline Scheduling Templates page, click Create Scheduling Template.

4. On the Create Offline Scheduling Template page, configure the following parameters.

   Templates support basic scheduling and conditional scheduling, each with different parameter configurations.

   Basic scheduling template

   Parameter	Description
   Template Name	Enter a template name. The name can contain any characters and cannot exceed 64 characters in length. The name must be unique within the tenant.
   Template Type	Select Basic Scheduling Template.
   Description	Enter a description for the basic scheduling template. The description cannot exceed 1,000 characters in length.
   Schedule Type	Three scheduling types are supported: Normal, Dry-Run, and Pause. Normal: The node is scheduled based on the time configuration of the scheduling cycle and is executed normally (processes data). This is the default option for tasks. Dry-Run: The node is scheduled based on the time configuration of the scheduling cycle but runs in dry-run mode (does not process data). When the node is scheduled, the system directly returns a success response without actually executing the task. This type is typically used when a node does not need to be executed for a certain period and should not block the execution of its downstream nodes. Pause: After this option is selected, the node is scheduled based on the time configuration of the scheduling cycle, but the node status is set to paused (does not process data). When the node is scheduled, the system directly returns a failure response and the descendant nodes cannot be run. This type is typically used when a task does not need to be executed temporarily but will be used later.
   Effective Date	Select the date range during which the template is effective, for example, 2025-05-01 ~ 2025-06-01.
   Recurrence	The scheduling cycle determines how often the task code runs in the production scheduling system. After a task is submitted, the system generates recurring instances starting from the next day based on the configured time attributes. Instances run based on upstream dependency results and the scheduled time point. The Recurrence options include Daily, Weekly, Monthly, Hourly, and By Minute: Daily: The scheduling task automatically runs once a day. When you create a recurring task, the system runs the task at 00:00 every day by default. You can click the icon to specify the time when the task runs. Weekly: The scheduling task automatically runs once at a specific time on specific days of each week. You can click the icon to specify the time when the task runs. Note To ensure that downstream instances run properly, the system generates instances at non-specified scheduling times, sets them as successfully run, and does not execute any logic or occupy resources. Monthly: The scheduling task automatically runs once at a specific time on specific days of each month. You can click the icon to specify the time when the task runs. Note To ensure that downstream instances run properly, the system generates instances every day at non-specified scheduling times, sets them as successfully run, and does not execute any logic or occupy resources. Hourly: The options include Time Period, Time Frame, Custom Time Period, and Custom Time Point. Time Period: The scheduling task automatically starts at the specified time interval within the specified time period every day. Click the icon to set the Start Time and End Time of the time period, and click the icon to select n-hour interval. For example, if the time period is set to 00:00 to 23:00 and the interval is set to 1 hour, the current task is automatically scheduled every hour from 00:00 to 23:00 every day. Time Frame: Click the drop-down list box to select Time Frame. The scheduling system automatically generates and runs instances for the task at the selected time frame. Custom Time Point: The scheduling system automatically generates and runs instances for the task at the selected custom time points. Click the drop-down list box to select custom time points. You can click +Add Custom Time Point to add multiple time points. Custom Time Period: The scheduling task automatically starts at the specified time interval within specific time periods every day. Click the icon to set the Start Time and End Time of the time period, and enter n-minute interval (n is an integer from 5 to 360) after the interval. You can click +Add Custom Time Period to add up to 10 time periods. The time periods cannot overlap. For example, for time period 1, if the time period is set to 00:00 to 03:00 and the interval is set to 30 minutes, the current task is automatically scheduled every 30 minutes from 00:00 to 03:00 every day. By Minute: The options include Daily and Hourly. Daily: The scheduling task runs at the specified time interval within the specified time period every day. Hourly: The scheduling task runs at the specified time interval from the specified start time of each hour to the end of the hour.
   Scheduling Plan	Click Preview. The scheduling plan displays all scheduling instances and their scheduling types for each day of a month based on the configured scheduling cycle. You can choose to preview dates by data timestamp or run date (scheduling date). Hover over the scheduling type module of a day to view the scheduling instance details for that day, including the run time, scheduling type, and condition name.

   Conditional scheduling template

   Parameter	Description
   Template Name	Enter a template name. The name can contain any characters and cannot exceed 64 characters in length. The name must be unique within the tenant.
   Template Type	Select Conditional Scheduling Template.
   Description	Enter a description for the conditional scheduling template. The description cannot exceed 1,000 characters in length.
   Scheduling Condition	You can set up to 10 scheduling conditions. The system evaluates conditions in top-down order, executes the corresponding scheduling action when a condition is met, and stops evaluating subsequent conditions. If no conditions are met, the default scheduling configuration runs. Important Conditional scheduling takes effect only when the scheduling type is Normal. Click +Add Scheduling Condition. In the Edit Conditional Scheduling dialog box, configure the conditional scheduling information. Condition Name: The name can contain any characters and cannot exceed 32 characters in length. Status: Enabled by default. If disabled, this conditional scheduling is ignored during scheduling. Meet the Following Conditions: The judgment rule for the condition. When the condition is evaluated as true, the scheduling is performed based on the Execute Scheduling configuration. For configuration instructions, see Conditional scheduling rule description. Note Cross-node parameters are not supported as conditions. Execute Scheduling: Supports custom and follow scheduling properties: Custom: When the condition is evaluated as true, the scheduling runs based on the configured Schedule Type. Follow Scheduling Properties: Consistent with the scheduling strategy in the scheduling properties, equivalent to the scheduling settings when conditional scheduling is disabled. Schedule Type: Same as the scheduling type in the basic scheduling template. For configuration instructions, see . Start Time: Configure the start time for scheduling with this template. If a scheduling task uses this template for conditional scheduling on a certain day, the scheduling starts based on the time configured here. Note This item can be configured only when the scheduling type is Normal. If the start time configured for a daily scheduling task is earlier than the start time configured here, the time configured for the task takes precedence. Click OK.
   Scheduling Plan	Click Preview. The scheduling plan displays all scheduling instances and their scheduling types for each day of a month based on the configured conditional scheduling. You can choose to preview dates by data timestamp or run date (scheduling date). Hover over the scheduling type module of a day to view the scheduling instance details for that day, including the run time, scheduling type, and condition name.

5. Click OK to complete the template configuration.

Manage offline scheduling templates

1. On the Offline Scheduling Templates page, you can view the information of each offline scheduling template, including Template Name, Template Type, Created By, Created At, and Last Modified.

2. (Optional) You can search for templates by entering template name keywords or filter templates by template type.

3. In the Actions column of a target template, you can perform the following operations.

   Operation	Description
   Edit	You can edit all information except the template name and template type. After an offline template is edited, all production tasks that reference the template automatically use the latest configuration without resubmission or publishing.
   View Details	View the detailed information of the offline scheduling template. On the View Offline Scheduling Template page, click Preview to view the scheduling plan.
   View References	View the objects that reference the offline scheduling template. The Offline Scheduling Template References dialog box lists all referencing objects, including Object Name/ID, Project/Module, and File Format. Object Name/ID: When the object is a computing task or integration task, both the object name and ID are displayed. When the object is a logical table or derived metric, only the object name is displayed. Project/Module: When the object is a computing task or integration task, the project name is displayed. When the object is a logical table or derived metric, the module name is displayed. Note If the object belongs to a Dev-Prod project, the production and development environments are recorded separately. File Format: Includes computing task, integration task, logical table, and derived metric.
   Delete	You can delete only offline templates that are not referenced by any tasks.