Overview
The Schedule trigger runs a workflow automatically at a defined time or interval. Setting one up now has two modes: a Standard mode that builds the schedule for you from a few fields, and a CRON expression mode for writing the expression directly. Every schedule trigger also has its own Timezone, so a schedule stays anchored to local time year-round, including through Daylight Saving Time changes.
In this article, we'll be covering how to switch between Standard and CRON expression mode, how to set a schedule's timezone, how to build a schedule in Standard mode, how to preview upcoming trigger dates, and how Daylight Saving Time affects scheduled runs.
Switching between Standard and CRON expression mode
The Schedule trigger's configuration panel has two tabs: Standard and CRON expression. Both describe the same underlying schedule — switching tabs doesn't lose your configuration.
- Standard exposes the schedule as a set of fields (frequency, day, time) without requiring you to know CRON syntax.
- CRON expression exposes the raw expression directly, for schedules that Standard mode can't represent.
A new Schedule trigger opens in Standard mode by default, set to run every day at 12:00 AM. If a trigger already has a CRON expression that Standard mode can represent, it also opens in Standard mode. If the expression is more complex than Standard mode supports, the Standard tab is disabled with a tooltip explaining why: This CRON expression is too complex to show in standard view. Simplify it or clear it to switch back. Simplify or clear the expression on the CRON expression tab to re-enable Standard mode.
Setting a schedule's timezone
Every Schedule trigger has its own Timezone field, a searchable dropdown below the mode toggle. It applies to both Standard and CRON expression mode, and determines the actual local time your schedule runs at.
Timezone is set per trigger — there's currently no tenant-level default timezone, so each Schedule trigger's timezone has to be set individually.
Building a schedule in Standard mode
Start with the Every field to choose a frequency. The fields shown below it depend on which frequency you pick:
| Frequency | Additional fields |
|---|---|
| Minute | None — runs every minute. |
| Hour | Minute — which minute of the hour it runs on. |
| Day | At — the time of day it runs. |
| Week | On — which day(s) of the week; At — the time of day. |
| Month | On — which day(s) of the month; At — the time of day. |
- For Week and Month, On is a multi-select — you can pick more than one day. At least one day must stay selected.
-
At is a time-of-day field. You can type a time directly (e.g.
2:30 PM) or pick from the list, which browses in 15-minute increments.
Viewing upcoming trigger dates
An Upcoming trigger dates preview shows the next several times a schedule will actually fire, in the trigger's set timezone. This preview is available on the CRON expression tab — switch to it to see the equivalent CRON expression for whatever you built in Standard mode, along with its upcoming run dates.
The Upcoming trigger dates preview isn't currently shown while you're on the Standard tab. Switch to CRON expression to check it.
Understanding Daylight Saving Time behavior
Because a schedule runs in a fixed timezone, the twice-yearly clock change can affect runs set between 1:00 AM and 3:00 AM. Select Learn more next to the trigger's description at the top of the panel to open a summary of this behavior:
- Spring forward: the run for that day is skipped, then resumes normally the next day.
- Fall back: the run happens once as scheduled, but won't repeat when the clock passes that time again.
This only affects schedules set within the DST transition window — all other times run as expected.