Scheduling
Every campaign has a schedule that controls how its runs are triggered. The schedule is set on the basics step of the wizard and can be changed later by editing the campaign. This page covers the two schedule types, the repeat rules, the calendar preview, and how to skip an occurrence.
Schedule Types
| Type | Behaviour | Best for |
|---|---|---|
| Manual | Runs are created and started by you. Nothing sends automatically. | One-off sends, or campaigns without a fixed timetable. |
| Repeat | Runs are created and started automatically on your chosen cadence. Runs can still be created and started by hand at any time. | Repeat sends on a regular schedule. |
Choosing Manual keeps every send under your control: see Starting a Run for how to start runs yourself. The rest of this page covers Repeat schedules.
Configuring a Repeat Schedule
Selecting Repeat reveals a set of repeat controls:
| Field | Description |
|---|---|
| First Run | The date and time the first run occurs. This is the start boundary for the whole schedule. |
| Timezone | The timezone the schedule is anchored to. Defaults to your current timezone. Runs trigger at the correct local time regardless of server location. |
| Repeat Every | The interval and unit, for example every 1 Day, every 2 Weeks (fortnightly), every 3 Months. |
| In (Yearly only) | The month a yearly schedule runs in, for example December. |
| On | Which days within the interval the run occurs. See On day rules below. |
| End | When the schedule stops: No end, or a specific end date. |
As the schedule is configured, a plain-language summary updates beneath the controls, for example "Occurs every Weds at 9:30 AM, starting Weds, 15 April 2026."
On day rules
The On control changes with the repeat unit:
- Daily: no day selection. The run occurs every interval of days.
- Weekly: select one or more days of the week, Monday to Sunday. The run occurs on each selected day within the interval.
- Monthly and Yearly: choose either a static date, a fixed day of the month such as the 14th, or an ordinal position, a relative day such as the third Tuesday of the month.
Schedule Rules Reference
| Rule | What it controls | Example |
|---|---|---|
| Frequency | The primary unit of time: Daily, Weekly, Monthly or Yearly | Weekly |
| Interval | How many units pass before the run repeats | Every 2 weeks (fortnightly) |
| Weekly selection | Specific days of the week within an interval | Mon, Wed, Fri |
| Ordinal position | A day's relative position in the month | The second Tuesday of the month |
| Static date | A fixed calendar day for monthly or yearly repeats | Every 12th of the month |
| Month-end overflow | Handling for dates that do not exist in every month (29th to 31st) | Moves to the last day of the month |
| Start boundary | The fixed date and time the first run occurs | Starts 10 April at 09:00 |
| Time zone anchor | Keeps the schedule on its original local time across daylight saving | Always 09:00 AEST |
| Yearly month | For Yearly only, the month the campaign runs in | December |
Schedules are anchored to the timezone you choose, not to a fixed UTC offset. Runs trigger at the correct wall-clock time even across daylight saving transitions. Month-end overflow and ordinal rules are applied so a schedule never drifts or skips.
Schedule Preview (Calendar)
Both the campaign wizard and the campaign page preview the schedule as a calendar:
- Months can be navigated forward and back, and the calendar shows the timezone the schedule is anchored to, for example AEST (UTC+10).
- Days with a scheduled run are marked. Selecting a day shows the run's time and a subtitle describing how far away it is, for example "in 3 days", so timing is clear at a glance.
- Days without a scheduled run show "There is no run scheduled on this day."
The preview always opens in the campaign's own timezone, and closing and reopening it resets the timezone back to the campaign's. This applies in both the wizard and the campaign page, so the cadence you check is always the one that will be used.
Skipping a Scheduled Run
A single upcoming occurrence can be skipped without disabling the whole schedule:
- Open the schedule calendar, from the campaign wizard or the campaign page.
- Select the day of the occurrence to skip.
- Select Skip Run and confirm the cancellation.
The confirmation step applies in both places the calendar appears, so an occurrence cannot be skipped by accident. When an occurrence is skipped, nothing happens on that date and time: no run is created or started. All other occurrences continue as normal.
Editing a Schedule Clears Skips
Editing a campaign's schedule clears any previously skipped or overridden occurrences, so the updated schedule applies cleanly from that point. The wizard shows a warning when the schedule changes: "Changing your campaign schedule will reset any previously skipped dates."
Manual Runs Alongside a Repeat Schedule
A Repeat schedule does not stop you starting runs by hand. A run can be created and started at any time in addition to the automated cadence. Automatically created runs are named {Campaign Name} - Run and attributed to System Scheduled: see Campaign Runs for the difference between system and user runs.
Next Steps
- Campaign Runs. What each run does and how its lifecycle works
- Starting a Run. Starting runs now or later
- Creating a Campaign. Where the schedule is chosen