Automating when workflows run
Cron, interval, one-time, and calendar triggers, business hours and holiday gating, and execution history — what each does and how to use it.
This page covers the Scheduler — automating when a Mission runs or a Blueprint publishes. For how to build and run the workflow itself, see the Workflow Guide.
What is the Scheduler?
The Scheduler automates when something happens — it doesn't define what a workflow does (that's a Blueprint) or run it (that's a Mission). A schedule fires on the timer you configure, and either starts a Mission run or publishes a Blueprint version, exactly as if you had clicked the button yourself.
Find it under Workflow Studio → Scheduler.
Creating a schedule
- Open Workflow Studio → Scheduler and click Create schedule.
- Choose the Mission the schedule applies to.
- Under What should happen, choose Start a mission run or Publish a blueprint version — publishing also asks which Blueprint and version.
- Pick a trigger type and fill in its configuration (see below), then a timezone.
- Click Create schedule. You can edit, pause, resume, or delete it any time from the list.
Trigger types
Cron schedule — a standard five-field cron expression (minute hour day-of-month month day-of-week), e.g. 0 9 * * 1-5 for 9am on weekdays.
Fixed interval — fires every N seconds, on a fixed grid (not counted from when you created it).
One-time (delayed) — fires exactly once, at a date and time you choose.
Calendar dates — an explicit list of specific dates and times you add one at a time. This does not yet support recurrence rules (e.g. "every third Tuesday") — use Cron for recurring patterns.
Business hours & holidays
Check Only run during configured business hours on a schedule to gate it against the windows you set up in the Business Hours tab. A tick that falls outside every window is skipped, not delayed.
Check Skip configured holidays to gate against the dates you add in the Holidays tab.
A business-hours window can also be marked maintenance window — that blocks every schedule during that time, not only ones that opted into business-hours gating.
Both business-hours windows and holidays can apply to your whole organization by default, or be scoped to just the current workspace.
Execution history
Click History on any schedule to see every time it was due — whether it actually fired or was skipped, and why (paused, a maintenance window, a holiday, outside business hours, or the run/publish itself being refused). Every tick is recorded, so "why didn't this run?" is always answerable.
A schedule can never fire the same tick twice, even if you refresh or click quickly — Genesis records each due instant exactly once.
Frequently Asked Questions
Who can create or edit schedules? Workspace members and above. Managing business-hours and holiday calendars is restricted to workspace admins.
Does deleting a schedule affect a run it already started? No — the schedule only controls future ticks. A Mission run it already started keeps going independently.
Can I schedule a workflow to run on a recurring calendar pattern, like every third Tuesday? Not directly yet — Calendar dates take an explicit list, not a recurrence rule. Most recurring patterns can be expressed as a Cron expression instead.