Configure logical table scheduling properties

Scheduling properties define the scheduling rules for logical dimension tables and logical fact tables. Configure these properties to control how and when logical table tasks run in the production environment.

Procedure

1. Navigate to the Dataphin home page, select Development > Data Development from the top menu bar.

2. On the Development page, select Project from the top menu bar.

3. In the left-side navigation pane, choose Standard Modeling > Logical Dimension Table or Logical Fact Table. Then click on the desired logical table name in the Logical Table list.

4. Click Scan Configuration in the top menu bar of the logical table tab to open the Scan Configuration panel.

5. Within the Scan Configuration panel, set the necessary parameters in the Scheduling Properties section.

   Parameter	Description
   Schedule Type	The following scheduling types are available: normal scheduling, dry-run scheduling, and skip execution. Normal Scheduling: Runs the task on its configured schedule and executes real data. This is the default option for most tasks. Dry-run Scheduling: Runs the task on its configured schedule, but all executions are simulated (no real data is processed). The task returns success immediately without executing. Use this when a node does not need to run for a period and should not block its descendant nodes. Skip Execution: Runs the task on its configured schedule, but sets the node status to paused (no real data is processed). The task returns a failure response, and descendant nodes cannot run. Use this when a task is temporarily inactive but will be needed again later.
   Priority	Set the priority of the logical table to Medium, Low, or Lowest. The default priority for new logical tables is inherited from Management Hub > Development Platform Settings > Node Task Related Settings. Note After the logical table is published to the production environment or submitted in the Basic environment, the priority cannot be modified during editing. You must modify it in the production environment's operations. The priority value reflects the latest value in the production environment.
   Recurrence	The scheduling period determines how often the logical table task runs in the production environment. After a logical table task is submitted, task scheduling is configured based on the task's time attributes starting from the next day, generating recurring instances for automatic scheduling. Each instance runs based on the results of upstream dependencies and the configured time points. The available scheduling periods are Day, Hour, and Minute, determined by the Data Timeliness selected when the logical table is created. The scheduling type does not support modification. Daily Scheduling: The task runs automatically once a day. For logical tables with Offline T+1 Data Timeliness, the default schedule is 00:00 daily. Click the icon to modify the start time. Hourly Scheduling: The task runs once every hour. The start time cannot be modified. Minute Scheduling: The task runs once every 15 minutes. The start time cannot be modified. Note To ensure downstream instances run normally during non-specified scheduling times, the system generates instances every day and sets them to succeed without executing any logic or consuming resources.
   Scheduling Run Plan	Click Preview to view all scheduling instances and their scheduling types for each day of a month, based on the configured scheduling period and conditional scheduling rules. You can select Data Timestamp or Run Date (Scheduling Date) as the preview date type. If a single day has instances with different scheduling types, all types are shown by color, with the name and instance count for each type. For example, on the 4th of a month, the task may have 44 normal scheduling instances, 2 paused instances, and 12 dry-run instances. Hover over a scheduling type on a specific day to view the detailed instance list, including scheduling type, scheduling conditions, and condition names.
   Conditional Scheduling	After enabling conditional scheduling, select a Configuration Method: Custom Settings or Scheduling Template. Important You can define up to 10 groups of scheduling conditions. The system evaluates conditions from top to bottom. Once a condition is met, the corresponding scheduling action runs, and remaining conditions are skipped. If no conditions are met, the default scheduling configuration is used. Conditional scheduling takes effect only when the scheduling type is Normal Scheduling. Scheduling conditions and start times are calculated based on the configured Scheduling Time Zone. Custom Settings Click +add Scheduling Condition. In the Edit Conditional Scheduling dialog box, configure the following parameters: Condition Name: Any characters, up to 32 characters. Effective Status: Enabled by default. When disabled, this condition is skipped during scheduling. Meet the Following Conditions: Defines the condition rule. When the condition evaluates to true, scheduling runs according to the Execute Scheduling configuration. For details, see Conditional Scheduling Rule Description. Execute Scheduling: Choose between custom settings and following scheduling properties: Custom: When the condition evaluates to true, the task runs according to the configured Scheduling Type. Follow Scheduling Properties: Uses the same scheduling policy defined in the scheduling properties, equivalent to disabling conditional scheduling. Scheduling Type: For details, see Scheduling Type. Start Time: The time when the logical table task begins running. When the scheduling type is Normal Scheduling and Daily Scheduling, the start time defaults to 00:00 and can be modified. Click OK. After configuring conditional scheduling, click Preview Scheduling Run Plan to view the dates affected by conditional scheduling in the calendar. Important After modifying conditional scheduling settings, submitting and publishing to the production environment takes effect immediately for instances in the Not Running status. It does not take effect for instances that have already entered the Waiting for Run Time status. When using cross-node parameter judgment types in conditional scheduling, you must provide possible parameter values for preview. Scheduling Template After selecting Scheduling Template, choose from the Conditional Scheduling Templates configured in Planning > Common Business Logic > Offline Scheduling Templates. If no template meets your requirements, click Create Scheduling Template to create one. After selecting a template, you cannot add new scheduling conditions. Click the View Details icon next to each scheduling condition to view its details. Note If the current task's scheduling period is Day, Week, or Month, then the Start Time parameter in the referenced conditional scheduling template will take effect. If the current task's scheduling period is Hour or Minute, then the Start Time parameter will not take effect.

6. Click Save.