The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Execution Time
One-off tasks support specifying to year, month, day, hour, minute, and second.
Notes:
One-off tasks cannot generate new instances by resubmission after completion. You need to create a new task to repeat execution.
Minute Scheduling
Parameter description:
Parameter
Description
Configuration Method
The task configuration for each task is selected as normal by default and cannot be modified.
Scheduling Cycle
The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Effective Time
The effective time period of the scheduling time configuration. The system will perform auto-scheduling within this time range according to the time configuration. After the validity period expires, there will be no more auto-scheduling. The start date can only be a date after the current date. By default, the current date to 2099-12-31 is displayed.
Execution Time
The execution time of minute-based tasks can only be on the hour. Interval range: 5, 10, 15, 20, 30 minutes. Minute-based tasks generate instances according to the execution time for scheduling.
Hourly Scheduling
Parameter description:
Parameter
Description
Configuration Method
The task configuration for each task is selected as normal by default and cannot be modified.
Scheduling Cycle
The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Effective Time
The effective time period of the scheduling time configuration. The system will perform auto-scheduling within this time range according to the time configuration. After the validity period expires, there will be no more auto-scheduling. Only a start date can be selected.
Execution Time (choose one with the specified time)
Execution Time
For hourly tasks, the execution time can be set in time division. Interval range: 1 - 23 hours. Tasks generate instances according to the execution time for scheduling.
Interval Time
Control the instance generation frequency of tasks at the set interval time within the designated execution time interval.
Specified Time (choose one with the execution time)
specified time
Specified time range 0 - 23 o'clock, support multiple selections. Hourly tasks generate instances according to the specified time and execute.
designated minute
Specify the exact minutes for instance generation after the specified time.
Daily Scheduling
Parameter description:
Parameter
Description
Configuration Method
Support general and crontab configuration modes. The task configuration for each task is selected as general by default and cannot be modified.
Scheduling Cycle
The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Effective Time
The effective time period of the scheduling time configuration. The system will perform auto-scheduling within this time range according to the time configuration. After the validity period expires, there will be no more auto-scheduling. The start date can only be a date after the current date. By default, the current date to 2099-12-31 is displayed.
Execution Time
For daily tasks, the execution time can be set in time division. Instances generated will start execution upon reaching the execution time.
Weekly Scheduling
Parameter description:
Parameter
Description
Configuration Method
Support general and crontab configuration modes. The task configuration for each task is selected as general by default and cannot be modified.
Scheduling Cycle
The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Effective Time
The effective time period of the scheduling time configuration. The system will perform auto-scheduling within this time range according to the time configuration. After the validity period expires, there will be no more auto-scheduling. The start date can only be a date after the current date. By default, the current date to 2099-12-31 is displayed.
Specify Date
The specified date range for weekly tasks is from Monday to Sunday, supporting multiple selections.
Execution Time
For weekly tasks, the execution time can be set in time division. Generated instances will start execution upon reaching the specified execution time.
Monthly Scheduling
Parameter description:
Parameter
Description
Configuration Method
Support general and crontab configuration modes. The task configuration for each task is selected as general by default and cannot be modified.
Scheduling Cycle
The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Effective Time
The effective time period of the scheduling time configuration. The system will perform auto-scheduling within this time range according to the time configuration. After the validity period expires, there will be no more auto-scheduling. The start date can only be a date after the current date. By default, the current date to 2099-12-31 is displayed.
Specify Date
The specified date range for monthly tasks is from the 1st to the 31st of each month, supporting multiple selections. Note: The option for end of month and other dates are mutually exclusive.
Execution Time
For monthly tasks, the execution time can be selected in time division. Generated instances will start execution upon reaching the specified execution time.
Annual Scheduling
Parameter description:
Parameter
Description
Configuration Method
Support general and crontab configuration modes. The task configuration for each task is selected as general by default and cannot be modified.
Scheduling Cycle
The execution cycle units of task scheduling support minute, hour, day, week, month, year and one-time scheduling.
Scheduling Time Zone
Supports configuring the scheduling time zone. Tasks will be executed according to the corresponding execution time of the scheduling time zone.
The scheduling time zone is effective only for the scheduling time. For engine-side functions used in tasks, such as CURRENT_DATE, the time zone configured on the engine side is used (please clarify whether the engine time zone meets expectations).
Effective Time
The effective time period of the scheduling time configuration. The system will perform auto-scheduling within this time range according to the time configuration. After the validity period expires, there will be no more auto-scheduling. The start date can only be a date after the current date. By default, the current date to 2099-12-31 is displayed.
Specify Month
The specified month range for annual tasks is from January to December, supporting multiple selections.
Specify Date
The specified date range for annual tasks is from the 1st to the 31st, supporting multiple selections. Note: The option for end of month and other dates are mutually exclusive.
Execution Time
For annual tasks, the execution time can be selected in time division. Generated instances will start execution upon reaching the specified execution time of the specified month and date.
Scheduling Type
Support selection of normal scheduling and dry-run scheduling. Dry-run scheduling means that when scheduling to the task, 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
Dependency configuration supports configuring upstream and downstream dependencies for task nodes and the execution order of task instances.
Parameter description:
Info
Description
Self-dependency
Self-dependency refers to the dependency between instances in the same task.
Parallel
There is no dependency relationship between the previous and next cycle instances. If a task has multiple instances, multiple instances run simultaneously.
Unordered serial
No dependency between the current instance and the previous cycle instance. If a task has multiple instances, the system randomly selects an instance to run. Only one instance is in the running state at a time.
Ordered serial
The current instance depends on the status of the previous cycle instance.
Workflow self-dependency
Task scheduling has no workflow self-dependency configuration.
Upstream dependency tasks
Search for upstream dependency tasks
Support searching for upstream dependency tasks that need to be configured by task name, task ID, and project name.
Upstream dependency task list
When adding the searched task as a dependency task, the information of the corresponding task will be displayed in the dependency task list, including task name, task status, scheduling cycle, responsible person, associated workflow, associated project, time dimension, instance scope, execution policy, and delete.
The detailed parameter description is as follows:
Task name: task name, task ID, and task type of the dependency task.
Status of tasks: scheduling running status of dependency tasks.
Scheduling cycle: scheduling cycle of the dependency task.
Responsible person: the responsible person of the dependency task.
Associated workflow: data workflow that the dependency task belongs to.
Associated project: project of the dependency task.
Setting method: Recommendation strategy: Include commonly used dependency configurations; Customization: Users customize dependency configurations as needed.
Time dimension / Instance range
If you select the recommendation strategy: select the dependency mode and range. The selectable values for tasks in different cycles are different. See the table below for detailed configuration items: Scheduling dependency note.
If you select customization:
Interval mode: The input format is: x, y. It indicates the range of time offsets for dependency on upstream task instance data. For example, in the case of an interval (day), if you input -10, -1, it means a closed interval of instances that depend on the upstream task from 10 days ago to 1 day ago. x <= y, and the maximum difference is 1000.
List mode: The input format is: x, y, z. It indicates the specific offset values for dependency on upstream task instance data. For example, in the case of a list (day), if you input -3, -2, -1, it means dependency on instances from 3 days ago, 2 days ago, and 1 day ago of the upstream task. x < y < z, and a maximum of 50 specific time offset values can be entered.
Execution policy: Processing policy when dependent upstream task instance does not exist, defaults to waiting for upstream; waiting for upstream means persistently waiting when the upstream task instance does not exist, normal execution means executing normally when the upstream task instance does not exist.
Perform operations
Dependency preview: Supports previewing dependency results based on configured dependency relationships to assist users in judging whether the configured dependency relationships are as expected. Selectable start scheduling time to check corresponding instance data time and dependent instance list (instance data time).
Delete: After successful deletion, submission is required for it to take effect in production status.
Automatic Dependency Parsing
Provide the automatic dependency parsing feature to help users quickly configure dependency relationships. The usage method is as follows.
Step 1: Ensure that the output registration of upstream tasks has been configured. See below for specific configuration methods.
Step 2: Click Automatic Parsing in the current task.
Step 3: Select the tasks to depend on.
Dependency on Downstream Task
Dependence on downstream tasks means that the current task can select tasks from all downstream (including indirect downstream) to depend on, used for meeting users' some special dependency scenarios.
For example: Task A is the upstream task of Task B. Periodic Instance B1 depends on Periodic Instance A1. Periodic Instance A1 wants to depend on Periodic Instance B2, that is, the configuration on tasks is A depending on B and B depending on A. Then you can configure Task B in the scheduling configuration - dependency on upstream task of Task A.
Circular dependency relationships can exist between tasks, but cannot exist between instances. Therefore, the system will periodically detect the dependency relationships of instances. After the task is launched, if there is circular dependency on the instance, an alarm will be sent to you via email and SMS.
<Scheduling Dependency Note>
Cycle
Upstream
Minute
Hour
Day
Week
Month
Year
one-time
Minute
(By minute/current minute): Instances that depend on the same data time.
(By minute/previous period: Instances that depend on the previous data time.)
For minute-based tasks within an hour, all need to wait until the hourly task operation is completed before they can run.
(all minutely tasks within a day need to run only after the daily task is completed.)
(all minutely tasks within a week have to wait until the weekly task is completed before they can run.)
All minute-based tasks within month need to wait until the monthly tasks are completed before they can run.
All minute-based tasks within the year have to wait until the annual task is completed before they can run.
All minute instances depend on one-time task instances, irrespective of data time.
Hour
(billed hourly/in the previous hour (-60,0]): depend on all upstream instances in the previous hour (-60,0].
(billed hourly / in the previous hour): dependent on all upstream instances in [-60,0) in the previous hour.
(billed/pay-as-you-go) hourly/current hour: dependent on all upstream minute instances within the current hour.
(Billed hourly / Most recent instance): Depend on the instance of the last data time. First check [00:00 of the day, current system time]. If not found, then check [current time, 00:00 of the next day).
(all hourly tasks on a day can only run after the daily task is completed.)
Hourly tasks within a week have to wait until the weekly task is completed before they can run.
Hourly tasks within a month need to run only after the monthly tasks are completed.
(all hourly tasks within the year have to wait until the annual task is completed before they can run.)
ALL hourly instances depend on one-time task instances, unrelated to data time.
Day
(1)By day/previous day (-24*60,0]: Depends on all upstream instances within (-24*60,0] of the previous day.
(2)By day/previous day: Depends on all upstream instances within [-24*60,0) of the previous day.
(3)By day/on the day: Depends on all upstream minute instances within the day.
(1)By day/previous day (-24*60,0]:
(2)By day/previous day:
(3)By day/on the day: Depends on all upstream hourly instances within the day.
(1)By day/on the day: Depends on upstream daily instances within the day.
(1)By week/this week: All day tasks within a week have to wait until the weekly task is completed before they can run.
(2)By day/instance of the last data time: Depends on the current system time and the instance of the last data time before that.
(1)By month/this month: All daily tasks within a month need to wait until the monthly task is completed before they can run.
(2)By day/instance of the last data time: Depends on the current system time and the instance of the last data time before that.
(1)By year/this year: All daily tasks within the year need to wait until the annual task is completed before they can run.
All daily instances depend on one-time task instances, irrespective of data time.
Week
(1)By week/last week: Depend on all minutely task instances within last week.
(2)By week/this week: Depend on all minutely task instances within this week.
(1)By week/last week: Depend on all hourly task instances within last week.
(2)By week/this week: Depend on all hourly task instances within this week.
(1)By week/last week: Depend on all daily task instances of last week.
(2)By week/last friday: Depend on the instances of daily task instances last friday.
(3)By week/last Sunday: Depend on the instances of daily task instances last Sunday.
(4)By week/this week: Depend on all daily task instances of this week.
(5)By day/on the day: Depend on the instances of daily task on the day.
(6)By day/previous day: Depend on the instances of daily task on the previous day.
(1)By week/this week: Depend on all daily task instances of this week.
(2)By day/instance of the last data time: Depends on the current system time and the instance of the last data time before that.
(1)By month/this month: All weekly tasks within a month can only run after the monthly tasks are completed.
(2)By day/instance of the last data time: Depends on the current system time and the instance of the last data time before that.
(1)By year/this year: All weekly tasks within the year have to wait for the annual task to be completed before they can run.
ALL weekly instances depend on one-time task instances, irrespective of data time.
Month
(1)By month/last month: Depend on all minute-level task instances within last month.
(2)By month/this month: Depend on all minute-level task instances within this month.
(1)By month/last month: Depend on all hourly task instances within 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 last month.
(2)By month/end of last month: Depend on instances of last day of last month.
(3)By month/this month: Depend on all daily task instances within this month.
(4)By day/on the day: Depend on the instances of daily task on the day.
(5)By day/previous day: Depend on the instances of daily task on the previous day.
(1)By month/last month: Depend on all weekly task instances within last month.
(2)By month/this month: Depend on all weekly task instances within this month.
(3)By day/instance of the last data time: Depends on the current system time and the instance of the last data time before that.
(1)By month/this month: Depend on all monthly task instances within this month.
(2)By day/instance of the last data time: Depends on the current system time and the instance of the last data time before that.
(1)By year/this year: All tasks within the year have to wait for the annual task to be completed before they can run.
All monthly instances depend on one-time task instances, irrespective of data time.
Year
(1)By year/this year: Depend on all minutely task instances within this year.
(1)By year/this year: Depend on all hourly task instances within this year.
(1)By day/all days this year: Depend on all daily task instances within this year.
(2)By day/on the day: Depend on the daily instance of the same data time.
(3)By day/the previous day: Depend on the instance of the data time of the previous day.
(1)By year/this year: Depend on all weekly task instances within this year.
(1)By month/all months 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 monthly task instances of last day of last month.
(5)By month/beginning of last month: Depend on monthly task instances of 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 one-time task instances, irrespective of data time.
one-time
(1)By day/on the day:
All minutely task instances within the specified date.
(1) Daily/on the day: Default cross-cycle: Depend on all hourly task instances on the day of the specified time.
(1) Daily/on the day: Depend on daily task instances within the specified date.
(1) Weekly/this week: One-time tasks within a week can only run after the weekly task is completed.
(1) Monthly/this month: One-time tasks within a month can only run after the monthly task is completed.
(1) Yearly/this year: One-time tasks within a year can only run after the annual task is completed.
Depend on one-time task instances, irrespective of data time.
Output Registration
Supports configuration of the data table generated by the current task. Two configurations are provided:
Manual addition: click Add, fill in the output data table database, output data table, and output table partition (partition is optional).
Automatic parsing: click Automatic Parsing, and the system will automatically parse the information of the output table and fill it in.
