Dataphin:Configure offline pipeline scheduling

Configure scheduling rules for recurring offline pipeline tasks, including execution frequency, dependencies, and conditional scheduling.

Background information

• Dependencies define relationships between nodes. An ancestor node's status determines whether its descendant nodes can run.

• For dependent nodes: a descendant node runs only after its ancestor node completes, and then only at its scheduled time.

• Configurations submitted before the scheduled time take effect on schedule. Dependencies configured after the scheduled time generate instances only after a one-day delay.

Procedure

1. On the Dataphin homepage, in the top menu bar, select Development > Data Integration.

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

3. In the left navigation pane, choose Integration>Offline Integration, then click the target task in the Offline Integration list.

4. On the node tab, click Property on the right to open the Property panel.

5. On the Scheduling Configuration tab, configure the parameters in the Scheduling Configuration section.

   Parameter	Description
   Configuration Method	You can select Custom Configuration or Schedule Template. If you select Scheduling Template, choose from the Basic Scheduling Templates in Planning > Common Business Logic > Offline Scheduling Template, or click Create Scheduling Template to create one. With a template selected, Schedule Type, Effective Date, and Recurrence are locked, but you can still configure Priority, Rerun Property, and Conditional Scheduling.
   Schedule Type	Three scheduling types are available: Normal, Dry-Run, and Skip Execution. Normal: Runs on the configured schedule and processes actual data. This is the default type. Dry-Run: Runs on the configured schedule but skips actual data processing. The system returns success without executing the node. Use this type when a node does not need to execute for a certain period and should not block its descendant nodes. Skip Execution: The system schedules the node on its configured cycle but marks it as skipped (no actual data processing). The system returns failure and blocks dependent descendant nodes. Use this type when a node is temporarily not needed but will be used again later.
   Priority	Set the task priority to Medium, Low, or Lowest. The default priority is inherited from Management Hub > Development Platform Settings > Node Task-related Settings. Note After publishing to the production environment or submitting in the Basic environment, you cannot modify the priority during editing. Change it in O&M instead. The displayed priority reflects the latest production value.
   Scheduling Time Zone	The time zone configured for the tenant in Management Hub > System Settings > Tenant Settings > Basic Settings. Instance generation, scheduling cycle, and effective date use this time zone.
   Recurrence	Recurrence defines how often the node executes in the production scheduling system. After submission, the system generates recurring instances starting the next day based on the node's time properties. These instances run according to the results and timestamps of upstream dependent instances. Select a Recurrence frequency: Daily, Weekly, Monthly, Hourly, or Minutely. Daily: The node runs once a day, defaulting to 00:00. Click the icon to change the run time. Weekly: The node runs at a specific time on selected days of the week. Click the icon to configure. Note Outside scheduled times, the system generates placeholder instances marked as successful to unblock descendant nodes. No logic executes and no resources are consumed. Monthly: The node runs at a specific time on selected days of the month. Click the icon to configure. Note Outside scheduled days, the system generates daily placeholder instances marked as successful to unblock descendant nodes. No logic executes and no resources are consumed. Hourly: Supports scheduling by Time Range, Time Frame, Custom Time Range, and Custom Time Point. Time Range: The node runs at set intervals within a daily time range. Click the icon to set Start Time and End Time. Click the icon to select the Interval of n hours. Example: a range of 00:00–23:00 with a 1-hour interval runs the node every hour. On-the-hour: Select an On-the-hour time from the drop-down list. The system generates and runs an instance at the selected time. Custom Time Point: The system runs instances at selected custom time points. Select time points from the drop-down list, or click +Add Custom Time Point to add more. Custom Time Range: The node runs at set intervals within custom daily time ranges. Click the icon to set Start Time and End Time, then enter Interval of n minutes (5–360). Click +Add Custom Time Range to add up to 10 non-overlapping ranges. Example: a range of 00:00–03:00 with a 30-minute interval runs the node every 30 minutes in that window. Minute-level scheduling: supports Daily or Hourly. Daily: The node runs at the specified interval within the designated time range each day. Hourly: The node runs at the specified interval from the specified start time of each hour to the end of that hour.
   Scheduling Run Plan	Click Preview to view all scheduling instances and their types for each day of a selected month. Select Data Timestamp or Run Date (Scheduling Date) as the preview date type. If a day contains instances with different scheduling types, the system displays each type by color with the instance count. For example, the following figure shows 44 normal, 2 skipped, and 12 dry-run instances on the 4th. Hover over a day to view the instance list, including run time (based on the Scheduling Time Zone), scheduling type, and condition name.
   Conditional Scheduling	Enable conditional scheduling and select a Configuration Method: Custom Settings or Scheduling Template. Important The system supports up to 10 conditions, evaluated in top-to-bottom order. The first matching condition triggers its action and stops further evaluation. If no condition matches, the default configuration applies. Conditional scheduling takes effect only when the scheduling type is Normal. Conditions and start times use the configured Scheduling Time Zone. The system evaluates conditions at instance generation to determine the scheduling type. Custom Settings Click +Add Scheduling Condition. In the Edit Conditional Scheduling dialog box, configure the conditional scheduling information. Condition Name: Any characters, up to 32 characters. Status: Enabled by default. If disabled, the conditional schedule is ignored during scheduling. Meet the following conditions: The condition evaluation rule. If the condition is true, the system schedules per the Execute Schedule configuration. For configuration details, see Conditional Scheduling Rules. Execute Schedule: Two options: Custom: If the condition is true, the system uses the configured Scheduling Type. Follow Scheduling Property: Uses the same scheduling policy as when conditional scheduling is disabled. Scheduling Type: Same options as the Scheduling Type parameter above. Click OK. Click Preview Scheduling Run Plan to view the dates when conditions are met. Important After publishing modified conditional scheduling to production, changes apply immediately to instances in the Not Running state but not to instances already in Waiting for Run Time. If cross-node parameter judgment types are used in conditional scheduling, provide possible parameter values for preview. Scheduling Template After you select Scheduling Template, choose from the Conditional Scheduling Templates in Planning > Common Business Logic > Offline Scheduling Templates, or click Create Scheduling Template to create one. With a template selected, you cannot add new scheduling conditions. Click the View Details icon next to a condition to view its details. Note The Start Time parameter in the template takes effect only for Daily, Weekly, or Monthly schedules. For Hourly or Minutely schedules, Start Time is ignored.
   Cross-Tenant Dependency	Allows dependencies from nodes in other tenants. If enabled, select the Allowed Tenants. Only tenants in the same time zone as the current tenant are available. Note This option is configurable only if cross-tenant dependency is enabled for the current tenant.

6. Click OK to save the scheduling configuration.