Offline mode scheduling configuration
Scheduling configurations define how stream-batch integrated task nodes recur in the production environment. You can configure the scheduling period, effective date, and other properties in the task's configuration panel.
Procedure
-
Navigate to the Dataphin home page, and from the top menu bar, select Development > Data Development.
-
At the top menu bar of the Development page, choose Project.
-
In the left-side navigation pane, click on Data Processing > Script Task. Then, in the Script Task list, select the desired task name.
-
On the task tab, access the Configuration panel by clicking Configuration on the right.
-
Within the Configuration panel, select the Offline Mode tab. Proceed to the Scan Configuration section to input the necessary parameter information.
Parameter
Description
Time Attribute
Select a Time Attribute. The Time Attribute options are:
-
Normal: The task runs on its configured schedule. This is usually the default option.
-
Dry-Run: The task follows its configured schedule but is not actually executed. Each scheduled instance is immediately marked as successful without running.
Priority
Set the priority of the current real-time task in offline mode to Medium, Low, or Lowest.
For new real-time tasks, the default priority is inherited from Management Center > Development Platform Settings > Node Task Settings.
NoteAfter the task is published to the production environment or submitted in the Basic environment, the priority can only be modified in production operations. The priority value reflects the latest value in the production environment.
Paused
If Paused is set to Yes, the task follows its configured schedule but each instance immediately returns as failed without execution. Use this for tasks that are temporarily unneeded but will be reactivated later.
Recurrence
The scheduling period defines how often the task runs in the production environment. After a task is successfully submitted, the system generates recurring instances starting from the next day based on the time attribute configuration. Instances run according to upstream dependency results and the specified time points.
The Scheduling Period options include Daily, Weekly, Monthly, Hourly, and Minute:
-
Daily Scheduling: The task is automatically executed once a day. When creating a new recurring task, the system's default period is set to execute at 00:00 every day. You can specify the execution time by clicking the
icon. -
Weekly Scheduling: The task is automatically executed once on specific days of the week at specific times. You can specify the execution time by clicking the
icon.NoteTo ensure the normal operation of downstream instances outside the specified scheduling time, the system generates instances and directly marks them as successfully executed without performing any logic or consuming resources.
-
Monthly Scheduling: The task is automatically executed once on specific days of the month at specific times. You can specify the execution time by clicking the
icon.NoteTo ensure the normal operation of downstream instances outside the specified scheduling time, the system generates instances daily and directly marks them as successfully executed without performing any logic or consuming resources.
-
Hourly Scheduling: Supports Time Range, On the Hour, Custom Time Range, and Custom Time Points scheduling.
-
Time Range Scheduling: The task is automatically scheduled at specified intervals within a specified time range each day. Click the
icon to set the Start Time and End Time of the time range. Then, click the
icon to select the Interval (n hours). For example, if the time range is set to 00:00–23:00 and the interval is set to 1 hour, the task will be automatically scheduled every hour within the time range of 00:00–23:00 each day. -
On the Hour Scheduling: Select the On The Hour time from the drop-down list. The scheduling system will automatically generate and execute instances for the task at the selected hourly time.
-
Custom Time Points Scheduling: The scheduling system automatically generates and executes instances for the task at the selected custom time points. Select custom time points from the drop-down list. You can click + Add Custom Time Point to add multiple time points.
-
Custom Time Range Scheduling: The task is automatically scheduled at specified intervals within certain time ranges each day. Click the
icon to set the Start Time and End Time of the time range. Then, enter the Interval (n minutes) (n is an integer between 5 and 360). You can click + Add Custom Time Range to add up to 10 time ranges. The time ranges must not overlap. For example, if Time Range 1 is set to 00:00–03:00 with an interval of 30 minutes, the task will be automatically scheduled every 30 minutes within the time range of 00:00–03:00 each day.
-
-
Minute Scheduling: Supports Daily or Hourly.
-
Daily: The scheduling task runs once at the specified time interval within the daily time period.
-
Hourly: From the specified start time each hour to the end of that hour, the scheduled task runs once at the interval specified by the interval time number.
-
Scheduling Execution Plan
Click Preview to view all scheduling instances and their types for each day of a selected month. The preview date type can be Data Timestamp or Execution Date (Scheduling Date).
If a single day contains multiple scheduling types, the system color-codes each type and lists its name and count. For example, the following figure shows that on the 4th day of a month, the task has 44 normal 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 types, conditions, and condition names.
Depend On Previous Period
Specify whether the current period's node must wait for the previous period's node or other nodes to complete before it runs.
Select Custom or Current:
-
If the execution of the current period's node depends on whether the previous period's node successfully produces data, select Current. The current node will only start execution if the previous period's node is successfully executed.
-
If a code task does not use the output table of a certain node but requires dependency on whether the node successfully produces data in the previous period, select Custom node dependency.
-
-
To finalize the scheduling configuration for the real-time task in offline mode, click OK.