The scheduling policy supports either conventional periodic scheduling or one-time execution strategy.
One-Time Scheduling
Parameter description:
Parameters
Description
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Execution Time
One-time tasks can specify down to the year, month, day, hour, minute, and second.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Note:
Once a one-time task is completed, it cannot be resubmitted to generate a new instance. A new task needs to be created for repeated execution.
Minute Scheduling
Parameter description:
Parameters
Description
Configuration Method
The default selection for single task configuration is conventional and cannot be modified.
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Effective Time
The effective time period of the scheduling time configuration. The system will automatically schedule according to the time configuration within this range. Beyond the validity period, it will not schedule automatically. The start date can only be selected after the current date, defaulting from the current date to 2099-12-31.
Execution Time
The execution time for minute tasks can only be selected on the hour, with interval ranges of 5, 10, 15, 20, 30 minutes. Minute tasks generate instances based on the execution time for scheduling.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Hourly Scheduling
Parameter description:
Parameters
Description
Configuration Method
The default selection for single task configuration is conventional and cannot be modified.
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Effective Time
The effective time period for scheduling time configuration means that the system will automatically schedule tasks according to the time configuration within this time range. When the period exceeds, it will no longer automatically schedule. The start date can only be selected.
Execution Time (choose one with the specified time)
Execution Time
The hourly task execution time can be chosen in hours and minutes, with an interval range of 1-23 hours. Tasks generate instances based on the execution time for scheduling.
Interval time
Using the set interval time unit, control the task's instance generation frequency within the specified execution time range.
Specified Time (choose one with the execution time)
Specified time
The specified time range is from 0 to 23 o'clock, supporting multiple selections. Hourly tasks generate instances according to the specified time and execute.
Specified minutes
Specify the exact minutes after the specified time to generate instances.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Daily scheduling
Parameter description:
Parameters
Description
Configuration Method
Supports conventional and crontab configuration methods. The single task configuration defaults to conventional and cannot be modified.
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Effective Time
The effective time period of the scheduling time configuration. The system will automatically schedule according to the time configuration within this range. Beyond the validity period, it will not schedule automatically. The start date can only be selected after the current date, defaulting from the current date to 2099-12-31.
Execution Time
The daily task execution time can be chosen in hours and minutes. The generated instance will start executing upon reaching the execution time.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Weekly scheduling
Parameter description:
Parameters
Description
Configuration Method
Supports conventional and crontab configuration methods. The single task configuration defaults to conventional and cannot be modified.
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Effective Time
The effective time period of the scheduling time configuration. The system will automatically schedule according to the time configuration within this range. Beyond the validity period, it will not schedule automatically. The start date can only be selected after the current date, defaulting from the current date to 2099-12-31.
Specify Date
Weekly tasks can specify dates ranging from Monday to Sunday and support multiple selections.
Execution Time
The weekly task execution time can be chosen in hours and minutes. The generated instance will start executing upon reaching the specified date and time.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Monthly scheduling
Parameter description:
Parameters
Description
Configuration Method
Supports conventional and crontab configuration methods. The single task configuration defaults to conventional and cannot be modified.
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Effective Time
The effective time period of the scheduling time configuration. The system will automatically schedule according to the time configuration within this range. Beyond the validity period, it will not schedule automatically. The start date can only be selected after the current date, defaulting from the current date to 2099-12-31.
Specify Date
Monthly tasks can specify dates ranging from the 1st to the 31st of each month and support multiple selections. Note: Month-end options are mutually exclusive with other dates.
Execution Time
The monthly task execution time can be chosen in hours and minutes. The generated instance will start executing upon reaching the specified date and time.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Annual scheduling
Parameter description:
Parameters
Description
Configuration Method
Supports conventional and crontab configuration methods. The single task configuration defaults to conventional and cannot be modified.
Scheduling Cycle
The execution cycle unit for task scheduling supports minutes, hours, days, weeks, months, years, and one-time scheduling.
Effective Time
The effective time period of the scheduling time configuration. The system will automatically schedule according to the time configuration within this range. Beyond the validity period, it will not schedule automatically. The start date can only be selected after the current date, defaulting from the current date to 2099-12-31.
Specify Month
Annual tasks can specify months ranging from January to December and support multiple selections.
Specify Date
Annual tasks can specify dates ranging from the 1st to the 31st of each month and support multiple selections. Note: Month-end options are mutually exclusive with other dates.
Execution Time
The annual task execution time can be chosen in hours and minutes. The generated instance will start executing upon reaching the specified month, date, and time.
Scheduling Plan
Automatically generated based on the configured cycle and execution time.
Scheduling Type
Support selecting normal scheduling and dry-run scheduling. Dry-run scheduling means that when the task is scheduled, the system will directly mark the instance as successful without actually executing the task. Normal scheduling means executing the task code normally.
Scheduling dependency configuration
Dependency Configuration
The dependency configuration supports configuring upstream and downstream relationships and task instance execution order for task nodes.
Parameter description:
Information
Description(Optional)
Self-Dependency
(Self-Dependency refers to the dependencies between different instances within the same task)
Parallel
There is no dependency between instances of the previous period and the next period. If a task has multiple instances, they will run simultaneously.
Unordered Serial
There is no dependency between the current instance and the instance of the previous period. If a task has multiple instances, the system will randomly select one instance to run, and only one instance will be in running status at a time.
Ordered Serial
The current instance depends on the status of the instance from the previous period.
Workflow Self-Dependency
There is no workflow self-dependency configuration for task scheduling.
Upstream Dependency Task
Upstream Dependency Task Search
Supported by searching task name, task ID, and project name to find upstream dependency tasks that need to be configured.
Upstream Dependency Task List
When a searched task is added as a dependency task, the corresponding task information will be displayed in the dependency task list, including task name, task status, scheduling period, person in charge, workflow it belongs to, project it belongs to, time dimension, instance range, execution strategy, and delete operation.
The specific parameters are described as follows:
Task Name: Name, ID, and type of the dependency task.
Task Status: Scheduling operation status of the dependency task.
Scheduling Period: Scheduling period of the dependency task.
Person in Charge: Responsible person for the dependency task.
Workflow: Data workflow to which the dependency task belongs.
Project: Project to which the dependency task belongs.
Configuration Method: Recommendation Strategy: Includes common dependency configuration methods; Custom Definition: Users define dependency configuration as needed.
Time Dimension/Instance Range
If choosing Recommendation Strategy: Select dependency mode and range. Different periodic task dependencies have different selectable values. Detailed configuration items are shown in the table below: Scheduling Dependency Description.
If choosing Custom Definition:
Interval Mode: Input format is x,y representing the range of data time offsets of upstream task instances. For example, for daily intervals, entering -10,-1 means relying on upstream task instances from the previous 10 days to the previous day. x ≤ y, with a maximum difference of 1000.
List Mode: Input format is x,y,z representing specific offset values of data time of upstream task instances. For example, for daily lists, entering -3,-2,-1 means relying on upstream task instances from the previous 3, 2, and 1 days. x < y < z, with a maximum of 50 specific time offset values.
Execution Strategy: Handling strategy when upstream task instances do not exist; defaults to wait for upstream. 'Wait for Upstream' means to keep waiting if the upstream task instance doesn't exist, while 'Normal Execution' means to proceed even if the upstream task instance doesn't exist.
Operation
Dependency Preview: Supports previewing dependency results based on the configured dependency relationships, helping users determine if the configured dependencies meet expectations. Users can select the start scheduling time to view the list of dependent instances (instance data time).
Delete: After successful deletion, a submission is required to take effect in the production state.
Dependency on Downstream Task
Depending on downstream tasks means that the current task can select tasks from all downstream (including indirect downstream) to depend on, used to meet some special dependency scenarios for users.
For example: Task A is an upstream task of Task B. B1's cycle instance depends on A1's cycle instance. If A1's cycle instance wants to depend on B2's cycle instance, it means Task A depends on Task B and Task B depends on Task A as configured. This can be configured in the scheduling settings - Depend on upstream tasks for Task A.
There can be cyclic dependencies between tasks, but there can't be cyclic dependencies between instances. Therefore, the system will regularly check instances' dependencies. If there are cyclic dependencies between instances after the task goes online, alarms will be sent to you via email and SMS.
Scheduling Dependency Description
Cycle
Upstream
Minute
Hour
Day
Week
Month
Year
One-time
Minute
(1) By minute/current minute: Depend on instances at the same data timestamp.
(2) By minute/previous period: Depend on instances at the previous data timestamp.
(1) By hour/current hour: All minute tasks within the hour need to wait until the hourly task is completed before running.
(1) By day/current: All minute tasks within the day need to wait until the daily task is completed before running.
(1) By week/this week: All minute tasks within the week need to wait until the weekly task is completed before running.
(1) By month/this month: All minute tasks within the month need to wait until the monthly task is completed before running.
(1) By year/this year: All minute tasks within the year need to wait until the yearly task is completed before running.
All minute instances depend on the one-time task instance, regardless of the data timestamp.
Hour
(1) By hour/previous hour (-60,0]: Depend on all upstream instances within the previous hour (-60,0].
(2) By hour/previous hour: Depend on all upstream instances within the previous hour [-60,0).
(3) By hour/current hour: Depend on all upstream minute instances within the current hour.
(1) By hour/latest instance: Depend on the instance of the latest data timestamp. Priority is given to searching [Midnight of the Day, Current time], if not found, then search [Current time, Midnight of the Next Day).
(1) By day/today: All hourly tasks within the day need to wait until the daily task is completed before running.
(1) By week/this week: All hourly tasks within the week need to wait until the weekly task is completed before running.
(1) By month/this month: All hourly tasks within the month need to wait until the monthly task is completed before running.
(1) By year/this year: All hourly tasks within the year need to wait until the yearly task is completed before running.
All hourly instances depend on the one-time task instance, regardless of the data timestamp.
Day
(1) By day/previous day (-24*60,0]: Depend on all upstream instances within the previous day (-24*60,0].
(2) By day/previous day: Depend on all upstream instances within the previous day [-24*60,0).
(3) By day/today: Depend on all upstream minute instances within the day.
(1) By day/previous day (-24*60,0]:
(2) By day/previous day:
(3) By day/today: Depend on all upstream hourly instances within the day.
(1) By day/today: Depend on all upstream daily instances within the day.
(1) By week/this week: All daily tasks within the week need to wait until the weekly task is completed before running.
(2) By day/most recent data timestamp instance: Depend on the instance with the most recent data timestamp, including the current time.
(1) By month/this month: All daily tasks within the month need to wait until the monthly task is completed before running.
(2) By day/most recent data timestamp instance: Depend on the instance with the most recent data timestamp, including the current time.
(1) By year/this year: All daily tasks within the year need to wait until the yearly task is completed before running.
All daily instances depend on the one-time task instance, regardless of the data timestamp.
Week
(1) By week/previous week: Depend on all minute task instances within the previous week.
(2) By week/this week: Depend on all minute task instances within this week.
(1) By week/previous week: Depend on all hourly task instances within the previous week.
(2) By week/this week: Depend on all hourly task instances within this week.
(1) By week/previous week: Depend on all daily task instances within the previous week.
(2) By week/previous Friday: Depend on the daily task instance of the previous Friday.
(3) By week/previous Sunday: Depend on the daily task instance of the previous Sunday.
(4) By week/this week: Depend on all daily task instances within this week.
(5) By day/today: Depend on the daily task instance of today.
(6) By day/previous day: Depend on the daily task instance of the previous day.
(1) By week/this week: Depend on all daily task instances within this week.
(2) By day/most recent data timestamp instance: Depend on the instance with the most recent data timestamp, including the current time.
(1) By month/this month: All weekly tasks within the month need to wait until the monthly task is completed before running.
(2) By day/most recent data timestamp instance: Depend on the instance with the most recent data timestamp, including the current time.
(1) By year/this year: All weekly tasks within the year need to wait until the yearly task is completed before running.
All weekly instances depend on the one-time task instance, regardless of the data timestamp.
Month
(1) By month/last month: Depend on all minute task instances within the last month.
(2) By month/this month: Depend on all minute task instances within this month.
(1) By month/last month: Depend on all hourly task instances within the last month.
(2) By month/this month: Depend on all hourly task instances within this month.
(1) By month/last month: Depend on all daily task instances within the last month.
(2) By month/end of last month: Depend on the instance on the last day of the previous month.
(3) By month/this month: Depend on all daily task instances within this month.
(4) By day/today: Depend on the daily task instance of the current day.
(5) By day/previous day: Depend on the daily task instance of the previous day.
(1) By month/last month: Depend on all weekly task instances within the last month.
(2) By month/this month: Depend on all weekly task instances within this month.
(3) By day/most recent data timestamp instance: Depend on the instance with the most recent data timestamp, including the current time.
(1) By month/this month: Depend on all monthly task instances within this month.
(2) By day/most recent data timestamp instance: Depend on the instance with the most recent data timestamp, including the current time.
(1) By year/this year: All tasks within the year need to wait until the annual task is completed before running.
All monthly instances depend on the one-time task instance, regardless of the data timestamp.
Year
(1) By year/this year: Depend on all minute task instances within this year.
(1) By year/this year: Depend on all hourly task instances within this year.
(1) Daily/All days of this year: Depend on all daily task instances within this year.
(2) Daily/Current day: Depend on the daily instance at the same data time.
(3) Daily/Previous day: Depend on the instance with the previous day data time.
(1) By year/this year: Depend on all weekly task instances within this year.
(1) Monthly/All months of this year: Depend on all monthly task instances within this year.
(2) By month/this month: Depend on all monthly task instances within this month.
(3) By month/last month: Depend on all monthly task instances within last month.
(4) By month/end of last month: Depend on the monthly task instance on the last day of last month.
(5) By month/beginning of last month: Depend on the monthly task instance on the first day of last month.
(1) By year/this year: Depend on all upstream annual task instances within this year.
All annual instances depend on the one-time task instance, regardless of the data timestamp.
One-time
(1) By day/today:
Depend on all minute task instances within the specified date.
(1) By day/today: Cross-cycle default: Depend on all hourly task instances within the specified date.
(1) By day/today: Depend on daily task instances within the specified date.
(1) By week/this week: One-time tasks within the week need to wait until the weekly task is completed before running.
(1) By month/this month: One-time tasks within the month need to wait until the monthly task is completed before running.
(1) By year/this year: One-time tasks within the year need to wait until the annual task is completed before running.
Depend on the one-time task instance, regardless of the data timestamp.
Yes
No
Was this page helpful?