Task Scheduling

Overview

Task Scheduling supports daily, weekly, and monthly scheduled execution, as well as hour-level and minute-level Near Real-Time Scheduling. It also supports event-driven scheduling triggered immediately by upstream dataset updates, helping avoid empty task runs.

Configure Task Scheduling

1. Click an existing Offline Dev task to open the Scheduling Setting page.
2. Click Edit to configure task scheduling.

Scheduling Status

Choose whether scheduling should be enabled.

• When scheduling is enabled, the Offline Dev task is triggered automatically according to the configured scheduling mode.
• When scheduling is disabled, the system stops automatic execution. Manual runs and similar operations are not affected.

Scheduling Priority

When tasks are queued, Workflows with a higher priority run first. Workflows with the same priority are executed in first-in, first-out order.

Scheduling Mode

• Time-based Scheduling: Configure a schedule by interval in minutes, interval in hours, daily, weekly, monthly, or yearly mode. After scheduled execution is enabled, the system automatically triggers the Workflow at the specified time using the configured parameter values.

  

• After Datasets are updated: Its configuration and runtime behavior are equivalent to the ETL option After selected datasets are updated.

  

  After you select event scheduling, dataset updates can trigger Offline Dev scheduling. Completing another Offline Dev task can also trigger this task.

  • Trigger source

    • Dataset update: The platform automatically retrieves all input datasets from source ETLs in the workflow—that is, ETLs that have no scheduling dependencies and run in the first batch. If input replacement is configured, it retrieves the replacement datasets shown in the node configuration. Select the datasets that the workflow depends on. When a selected dataset updates, the platform checks whether the workflow run conditions are met and starts the workflow when they are.
    • Offline Dev task update: Click Add Task and select an Offline Dev task.
    

  • Trigger condition

    • Trigger after any selected dataset or task is updated:

      • The workflow runs when it receives an update event from any selected dataset or Offline Dev task.
      • The workflow can run again after its run conditions are met again.

    • Trigger after all selected datasets or tasks are updated:

      • The workflow runs after every selected dataset or Offline Dev task has updated.
      • The workflow can run again after its run conditions are met again.
      • If All datasets/tasks must be updated on the same day (00:00:00–23:29:59) is selected, the platform recalculates update status at midnight each day.
      

Time Window Restrictions

When scheduled execution is configured by interval in minutes or hours, or when event scheduling is used, you can configure one or more time ranges in which the task is allowed to run. Manual runs and URL triggers ignore these limits.

Skip Accumulated Instances

For interval schedules and event scheduling, enable Skip accumulated instances to cancel intermediate queued instances when a long-running instance causes a backlog. The platform runs the next scheduled instance automatically.

URL Trigger

External updates can be triggered through a URL. After the switch is enabled, the system provides a URL for updating the task, which contains verification information such as the task ID and update token.

Only POST requests are supported to trigger the task. When you need to assign values to task parameters, declare them in the request body. For example, to assign values to the aaa and bbb parameters, use the following request body:

{"params":[

{"name":"aaa","value":"456"},

{"name":"bbb","value":"789"}
]}

If no parameters are passed, the task runs using the default parameter values configured in the task.