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

• Scheduled Execution: 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.

  

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

  After event scheduling is selected, the system automatically retrieves all input datasets from the source ETL nodes in the Workflow, meaning the ETL nodes that have no upstream scheduling dependencies and run in the first batch. If input replacement has been configured, the replaced datasets shown in the node configuration are used instead.

  

  • Trigger conditions:

    • If the trigger condition is Trigger after any selected dataset is updated:

      • The Workflow is triggered after an update event is received for any selected dataset.
      • The workflow can be triggered again whenever the run conditions are satisfied again.

    • If the trigger condition is Trigger after all selected datasets are updated:

      • The Workflow is triggered after all selected datasets have been updated.
      • The workflow can be triggered again whenever the run conditions are satisfied again.
      • If All datasets must be updated on the same day (00:00:00-23:29:59) is selected, dataset update status is recalculated at midnight every day.

  • Select datasets: Choose the datasets that the workflow update depends on. When a selected dataset is updated, the system checks whether the target workflow's run conditions are satisfied. If they are, the workflow is triggered automatically.

  • Time 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. If the current time is outside the allowed range, the task does not run.
    

    

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.