Dataphin:Offline Task Scheduling Property Configuration

Procedure

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

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

3. In the left navigation pane, select Data Processing > Compute Task, and in the Compute Task list, click the name of the target task.

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

5. In the offline integration task Property panel, configure the parameters in the Scheduling Properties section.

   Parameter	Description
   Configuration Method	Select either Custom Configuration or Scheduling Template. If you select Scheduling Template, you can choose from all basic scheduling templates configured under Planning > Common Business Logic > Offline Scheduling Templates. If no suitable template exists, click Create Scheduling Template to create one. After selecting a template, the parameters Schedule Type, Effective Date, and Recurrence become read-only. You can still configure Priority, Rerun Properties, and Conditional Scheduling.
   Schedule Type	Three schedule types are supported: Normal, Dry-run, and Skip Execution. Normal: The task runs according to its scheduling cycle and executes real data processing. This is the default option for most tasks. Dry-run: The task is scheduled according to its cycle but does not process real data. When triggered, it immediately returns success without actual execution. Use this type when a node should not run for a period but must not block its downstream nodes. Skip Execution: The task is scheduled per its cycle, but its status is marked as paused (no real data processing occurs). When triggered, the system returns failure and blocks all downstream nodes that depend on it. Use this when a task is temporarily inactive but will be used again later.
   Priority	Set the priority for the current offline task. Options are Medium, Low, or Lowest. When creating a new offline task, the default priority comes from Management Hub > Development Platform Settings > Node Task Settings. Note After the task is published to the production environment or submitted in the Basic environment, you cannot edit its priority here. Modify it in production O&M instead. The displayed value reflects the latest priority in production.
   Effective Date	Once configured, the scheduling task runs automatically only within the effective date range. Tasks outside this range are not scheduled.
   Scheduling Time Zone	Displays the time zone configured in Management Hub > System Settings > Basic Settings. Instance generation time, scheduling cycles, and effective dates are all calculated using this time zone.
   Recurrence	The recurrence defines how often the task code runs in the production scheduling system. After successful submission, the system generates recurring instances starting the day after submission, based on the configured time attributes. These instances run according to upstream dependency results and timing. Choose from the following recurrence options: Daily, Weekly, Monthly, Hourly, and Minute: Daily: The task runs once every day. By default, new recurring tasks run at 00:00 daily. Click the icon to specify a different time. Weekly: The task runs once per week on selected days at a specified time. Click the icon to set the time. Note On non-scheduled days, the system creates an instance and marks it as successful without executing logic or consuming resources. This ensures downstream instances run normally. Monthly: The task runs once per month on selected days at a specified time. Click the icon to set the time. Note On non-scheduled days, the system creates a daily instance and marks it as successful without executing logic or consuming resources. This ensures downstream instances run normally. Hourly: Supports Time Frame, On the Hour, Custom Time Frame, and Custom Time Point scheduling. Time Frame: The task runs at regular intervals within a specified daily time window. Click the icon to set the Start Time and End Time. Click the icon to select Every n Hours. For example, if the time frame is 00:00–23:00 with a 1-hour interval, the task runs hourly throughout the day. On-the-hour scheduling: You can click the drop-down list box to select an On The Hour time. The scheduling system will then automatically generate an instance for the task and run it at the selected time. Custom Time Point: The system generates and runs instances at your selected custom times. Use the drop-down list to choose times, and click + Add Custom Time Point to add multiple points. Custom Time Frame: The task runs at regular intervals within user-defined daily time windows. Click the icon to set Start Time and End Time. Enter an interval of Every n Minutes (n must be an integer from 5 to 360). Click + Add Custom Time Frame to add up to 10 non-overlapping time frames. For example, if Time Frame 1 is 00:00–03:00 with a 30-minute interval, the task runs every 30 minutes during that window. Minute-level scheduling: Supports Daily or Hourly schedules. Daily: The task runs at fixed intervals within a specified daily time window. Hourly: The task runs at fixed intervals from a specified start minute until the end of each hour.
   Scheduling Run Plan	Click Preview to view all scheduled instances for a given month based on your recurrence and conditional scheduling settings. Choose to preview by Data Timestamp or Runtime (Scheduled Date). If multiple schedule types occur on the same day, the calendar displays all types using color coding, along with the count for each. For example, the image below shows that on the 4th of a month, the task has 44 normal instances, 2 skipped instances, and 12 dry-run instances. Hover your mouse over a day’s schedule block to see a detailed list of instances for that day, including runtime (based on the scheduling time zone), schedule type, and condition name.
   Conditional Scheduling	After enabling conditional scheduling, select a Configuration Method: Custom Settings or Scheduling Template. Important You can define up to 10 scheduling conditions. The system evaluates them top to bottom. When a condition matches, the corresponding action runs, and evaluation stops. If no condition matches, the default scheduling configuration applies. Conditional scheduling works only when the schedule type is Normal. All conditions and start times use the configured scheduling time zone. At instance generation, the system checks whether the instance matches any condition to determine its schedule type. Custom Settings Click + Add Scheduling Condition. In the Edit Conditional Scheduling dialog box, configure the following: Condition Name: Any characters allowed, up to 32 characters long. Status: Enabled by default. When disabled, the condition is ignored during scheduling. When the following condition is met: The rule used to evaluate the condition. If true, the task runs according to the Schedule Action settings. For details, see Conditional Scheduling Rule Description. Schedule Action: Choose between Custom and Follow Scheduling Properties: Custom: If the condition is met, run the task using the specified Schedule Type. Follow Scheduling Properties: Use the same schedule type defined in the main scheduling properties—equivalent to disabling conditional scheduling. Scheduling Type: For more information, see Scheduling Type. Click OK. After setting up conditional scheduling, click Preview Scheduling Run Plan to see which dates match your conditions on the calendar. Important After modifying conditional scheduling settings and publishing to production, changes apply immediately to instances that are not yet running. They do not affect instances already in waiting-to-run status. If your condition uses cross-node parameter evaluation, provide possible parameter values for accurate preview. Scheduling Template After selecting Scheduling Template, choose from all conditional scheduling templates under Planning > Common Business Logic > Offline Scheduling Templates. If none fit, click Create Scheduling Template to create one. After selection, you cannot add new conditions. Click the View Details icon next to any condition to see its full configuration. Note If the task’s recurrence is Daily, Weekly, or Monthly, the Start Time parameter in the referenced conditional scheduling template takes effect. If the recurrence is Hourly or Minute, the Start Time parameter is ignored.
   Cross-Tenant Dependency	Enable this to allow tasks from other tenants to depend on this task. If enabled, select one or more Dependable Tenants. Only tenants in the same time zone as the current tenant can be selected. Note This option is available only if cross-tenant dependency is enabled for the current tenant.

6. Click OK to complete the offline task scheduling property configuration.