< woml />
View on GitHub

<schedule>

<schedule> admits runs at planned calendar times using WOML Cron v1.

Why use it

Use it for work tied to wall-clock dates or times, especially when timezone and missed-occurrence behavior matter.

Common use cases

  • Run a report every morning in a named timezone.
  • Start daily or weekly maintenance.
  • Recover one missed occurrence after downtime.

Syntax

WOML
<schedule
  id="dailyReport"
  cron="0 8 * * *"
  timezone="Europe/Berlin"
  on-missed="run-once"
/>

Rules and behavior

  • id and five-field numeric cron are required.
  • timezone is an optional canonical IANA timezone and defaults to UTC.
  • on-missed is skip or run-once and defaults to skip.
  • Cron supports wildcards, lists, inclusive ranges, and /step; it does not support seconds, names, macros, wrapping ranges, or Quartz-only tokens.
  • The payload contains RFC 3339 UTC scheduledAt and triggeredAt values.