Data Management:UpdateTaskFlowSchedule

This operation updates the scheduling settings of a task flow in edit mode. You can configure timed scheduling, periodic scheduling, and event scheduling. Timed scheduling supports one-time or periodic scheduling. Event scheduling supports subscriptions to task flows and task flow nodes.
After the configuration is updated, republish and deploy the task flow. New task flow instances are then scheduled based on the updated scheduling settings.

Scheduling configuration metric description

Configure timed scheduling: supports periodic scheduling or one-time scheduling.

Required parameters:

• ScheduleSwitch: True

• TriggerType: Cron

• CronBeginDate

• CronEndDate

• CronStr

• CronType

• ScheduleParam: varies by day, week, month, or one-time scheduling.

Examples:

Daily scheduling:

{
    "triggerType":"0",
    "dateTime":"00:00"
}

Weekly scheduling: Sunday is 1, Monday is 2, ..., Saturday is 7.

{
    "triggerType":"0",
    "dateWeek":[
        "1",
        "5"
    ],
    "weekTime":"00:00"
}

Monthly scheduling:

{
    "triggerType":"0",
    "dateMonth":"1",
    "MonthTime":"00:00"
}

One-time scheduling:

{
    "triggerType":"1",
    "specificTime":"2022-09-02 00:00"
}

Metric description

1. CronStr: The actual scheduling of the task flow is determined by the CronStr value.

2. CronBeginDate and CronEndDate: For periodic scheduling, CronBeginDate, CronEndDate, and CronStr together define the task flow scheduling. If the time specified by CronStr falls within the time range defined by CronBeginDate and CronEndDate, the task is triggered.

3. CronType: Used for validation. Set this parameter based on the cycle defined by CronStr.

4. ScheduleParam: Set this parameter based on the scheduling defined by CronStr.

Configure event scheduling (automatic cross-task-flow triggering)

Required parameters:

• ScheduleSwitch: True

• TriggerType: Event

• ScheduleParam

Example:

{
    "triggerType":"2" // Set to 2 for event scheduling
    "deps":[ // Task flow and node subscription configuration
        {
            "eventType":1, // Subscription type: 0 for task flow; 1 for task node
            "lisDagId":12345, // The task flow that contains the subscribed node
            "lisNodeId":2134 // The ID of the subscribed node
        },
        {
            "eventType":0,
            "lisDagId":12343 // The ID of the subscribed task flow
        },
        {
            "eventType":0,
            "lisDagId":23456
        }
    ],
    "maxWait":21600 // The maximum wait time before all subscriptions above run successfully
}