Visual schedule picker
You can pick from hourly to yearly presets, write arbitrary cron, run every N minutes, or do a one-shot run. End conditions support an until-date or a max-runs limit, and you can preview the schedule before you commit.
Use case: Automation
Schedule it, fork it, let it clean up after itself
A saved flow can carry its own schedule. You define it with cron expressions or visual presets, set the IANA timezone, and choose a catch-up policy for missed runs. A background scheduler runs it in the desktop app, the server, and the CLI daemon.
Capabilities
Recurring execution, first class
Catch-up policies
For missed windows you can choose to skip them, run once, or run all of them. The timer advances before execution, so overlapping ticks cannot double-fire.
Audited unattended runs
Scheduled runs are saved to the same execution history and carry a scheduled trigger tag. That tag is metadata only, so it preserves the zero-egress boundary.
Parameterized provisioning
A manual process that used to take hours becomes one run you can watch. You set the variables up front, follow per-step progress, and get notified when the environment is ready.
Fleet-wide templates
You can clone a vetted template across the estate. One central update then reaches every instance on its next scheduled run.
Everywhere the core runs
The scheduler service runs in Flow Studio, Flow Server, and the standalone schedule daemon in Flow CLI.
Case studies
Cadence without babysitting
customer Automation
Scheduled, fleet-wide scans
A batch operator responsible for many LPARs
Run the same vetted scan across the whole estate on a schedule - and never let one back-level LPAR rot silently.
Manual relay times N LPARs becomes a schedule that runs itself
internal Automation
Fast, repeatable provisioning
A platform engineer who stands up test instances
Turn a multi-hour manual provisioning ritual into one parameterized, observable flow.
Hours of manual sequential steps become one parameterized run
internal IT & DevOps
Daily broken-build defense
A release/build manager accountable for the daily build's health
Surface every broken solution build the same day, with a ping - and keep the quota clean on its own.
Days-to-discovery becomes a same-evening pushed alert
Stop re-running it by hand
Add a Cron node, set the cadence, and review exceptions instead of green runs.