Schedules (cron)
How to write a repeating schedule for campaigns, journeys, audience syncs, connectors and agents, and what the fields mean.
Campaigns, journey schedule triggers, audience syncs, connector batches and agents all repeat on a schedule written as a cron expression. They share one rule, described here.
The five fields
A schedule has five fields separated by spaces:
| Field | Values |
|---|---|
| Minute | 0 to 59 |
| Hour | 0 to 23 |
| Day of month | 1 to 31 |
| Month | 1 to 12 |
| Day of week | 0 to 7 (0 and 7 are both Sunday) |
Each field accepts * (every value), a number, a range such as 1-5, a step such as */15 or 10-40/10, and a comma list such as 1,15.
These are not supported and are refused: shortcuts such as @daily, a seconds field, names such as MON or JAN, and the characters L, W, # and ?.
Day of month and day of week together
When you restrict both day of month and day of week, a day that matches either one fires. A field is restricted when it does not cover its whole range, so *, */1 and 1-31 are not restricted.
Example: 0 9 1,15 * 1-5 runs at 09:00 on the 1st, the 15th and every weekday.
Schedules that never occur
A schedule that can never fire, such as 0 0 30 2 * (30 February), is refused when you save it, with the message cron: expression never occurs. Add a weekday or pick a day that exists in the month.
Time zone
The schedule is read in the time zone stored with it. If you set none when you save in the console, the zone of your profile is used.
When the clocks go back, a time of day that happens twice runs once, the first time it occurs. When the clocks go forward, a time of day that is skipped does not run that day. In most of Europe and North America, for example, 30 2 * * * does not run on the day the clocks go forward and runs once at the first 02:30 when they go back.
Missed runs
If a campaign or audience sync was not running when it was due, it runs once for the most recent due time when it comes back, however long it was away. It does not replay the other missed times.
What changed
Since 2026-10-29 Campaign schedules use the same rule as connectors and agents. Before, a campaign with both day of month and day of week set ran only on days matching both.