Search documentation

Search for a topic, a control, or an event type.

    Docs / Workflows / Actions / Schedule

    Schedule

    Start recurring runs at specified times. A Schedule job supplies its own input instead of waiting for an incoming event.

    Expression and timezone

    The editor uses five cron fields, in this order: minute, hour, day of month, month and weekday. API configuration uses six fields with seconds first. The seconds field must be 0, so the shortest interval is one minute.

    cronExpression
    Supports * for every value, comma-separated values, ranges such as 1-5 and intervals such as */15. Weekdays use 0 for Sunday through 6 for Saturday.
    timezone
    An IANA timezone such as Europe/Stockholm. A 09:00 schedule follows local time in that zone rather than a fixed UTC hour.

    If both day of month and weekday are restricted, both must match. For example, day 15 and weekday 1 means the 15th only when it is a Monday.

    Weekday mornings

    This example starts a report at 09:00 Monday through Friday in Stockholm. The five-field editor expression is 0 9 * * 1-5. The API adds a leading 0 for seconds.

    Action configuration
    {
      "cronExpression": "0 0 9 * * 1-5",
      "timezone": "Europe/Stockholm",
      "properties": {
        "reportType": "daily"
      }
    }

    The report starts at 09:00 in winter and summer. Clock changes alter its UTC time. A local time skipped by a clock change has no matching occurrence.

    Automatic runs and missed occurrences

    A Schedule job has no trigger and starts the workflow at the times you set. Automatic starts use live jobs on the main workflow branch. Draft or paused workflows and feature-branch schedules do not start automatically.

    After a pause, the schedule resumes from the current time rather than replaying every occurrence during the pause. A delayed scheduler for a continuously live job can catch up due occurrences, up to 100 in one pass. Occurrences beyond that backlog cap can be skipped.

    A schedule is not a guarantee that every occurrence will execute. A claimed occurrence can be missed if its start cannot be published. Use execution history to check the runs that actually started.

    Time and output values

    The result includes scheduled_at, cron_expression, timezone, date and day_of_week, plus the configured properties. Configured properties with the same names replace built-in values. scheduled_at represents the scheduled occurrence, which can precede the actual start if the scheduler was delayed.

    scheduled_at, date and day_of_week follow the scheduled occurrence’s timezone. scheduled_at includes its UTC offset. timezone records the configured zone. day_of_week uses 0 for Sunday through 6 for Saturday. Map {{ action.scheduled_at }} and {{ action.reportType }} into the output event when a later report job needs them.