Weekday mornings
- One at a timeA new run waits until the last one finishes
- PacedOne start for each scheduled time
- Loop protectionPrevents a run from restarting its own schedule
Zero Scheduling
What is Zero Scheduling?
See how a schedule selects a target and cadence, controls overlapping starts, and records the work it starts or defers.
Four schedules
Weekday mornings
Every weekday at 09:00, starts Supplier review v3. Next: 09:00, the next weekday.
Every six hours
Every six hours, starts the Research agent. Next: 06:00, 12:00, 18:00, 00:00.
Sunday refresh
Every Sunday at 00:00, starts a refresh of the product catalogue dataset. Next: Sunday 00:00.
Month opening
The first working day of the month, starts Month opening v2. Next: 09:00 on the first working day.
Schedule
A flow version
An agent
A dataset refresh
A run
Started
Weekday mornings
CompletedStarted 09:00 · Supplier review v3Every six hours
RunningStarted 12:00 · Research agentSunday refresh
CompletedStarted 00:00 · Product catalogue
Managed starts
Every six hours
Deferred18:00 · While the earlier run remains openWeekday mornings
Stopped09:00 · Loop protection applied
What is a schedule?
A schedule is a trigger that starts work on a clock. You set when, in the terms your business already uses, and it starts the work at those times.
What can a schedule start?
A schedule can start a flow version, an agent, or a dataset refresh. Each target follows the cadence configured for it.
Can a schedule start work outside a flow?
Yes. It can start an individual agent or refresh a dataset as well as start a flow version.
How are overlapping starts handled?
Each schedule applies its configured start rate and concurrency setting. Loop protection detects a run that would retrigger its own schedule.
Schedule
A trigger that starts work on a clock.
Trigger
What starts a run: a schedule, an event, a webhook, or a direct call.
Run
One execution of a flow version, with a record of every step.
Zero Scheduling is part of Zero, the agentic orchestration platform.