Aller au contenu principal

Scheduler

Category: Trigger
Node id: scheduler

Handles scheduled execution with interval, one-time, or daily scheduling

What it does​

  • Interval-based scheduling with configurable seconds between runs
  • One-time execution at a specific RFC3339 timestamp
  • Daily execution at a configurable time of day (HH:MM)
  • Automatic next-run calculation and wait-time reporting
  • Idempotent one-time execution (prevents re-execution)
  • Last-run tracking to determine if execution is due

Use cases​

  • Run a data sync pipeline every 60 seconds
  • Schedule a one-time report generation at a specific date/time
  • Execute daily health checks or batch jobs at a fixed time
  • Control pipeline execution frequency in long-running workflows

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
last_runanyNoTimestamp of the last execution (for interval/daily)
executedbooleanNoWhether the one-time schedule has already executed

Output ports​

NameTypeRequiredDescription
should_executebooleanNoWhether the downstream pipeline should run now
schedule_typetextNoThe schedule type used
last_runanyNoTimestamp of this or previous run
next_runanyNoCalculated next run time
executed_atanyNoTimestamp of execution (when triggered)
wait_secondsnumberNoSeconds until next scheduled run (when not triggered)

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Schedule Typeschedule_typeenumNointervalinterval, once, dailyType of schedule
Interval (seconds)interval_secondsnumberNo60min 1Seconds between executions (for interval type)
Execute Atexecute_atstringNoRFC3339 timestamp for one-time execution
Time of Daytime_of_daystringNo00:00HH:MM format for daily execution

Errors​

CodeDescription
UNSUPPORTED_SCHEDULE_TYPESchedule type is not one of: interval, once, daily
INVALID_INTERVALinterval_seconds must be a positive number
MISSING_EXECUTE_ATexecute_at is required for one-time schedule but was empty
INVALID_RFC3339execute_at is not a valid RFC3339 timestamp
INVALID_TIME_OF_DAYtime_of_day is not in valid HH:MM format

Runtime notes​

  • should_execute is the primary output for controlling downstream execution
  • wait_seconds is only present when should_execute is false; executed_at only when true
  • For 'once' schedule, feed the executed output back into the executed input to prevent re-runs
  • last_run accepts both time.Time values and RFC3339 strings

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.