Routines
Scheduled Workflows That Never Miss a Beat
Define any workflow to run on a cron schedule. Routines handle timezones, catch up on missed windows, prevent overlapping runs, and log every execution.
Scheduler
00:00 06:00 12:00 18:00
SCHEDULER
Routine Tracks
security-audit 0 2 * * *
test-generation 0 9 * * 1
dependency-audit 0 3 * * 0
Recent Runs
✓
security-audit
✓
test-generation
✓
security-audit
✗
dependency-audit
✓
test-generation
① Clock ticks — sweep hand marks each scheduled trigger point on the timeline
② Routines fire — cron expressions trigger security-audit, test-gen, and dep-audit runs
③ History logged — completed runs show duration, cost, and next scheduled time
Built for Reliability
5-Field Cron
Standard cron syntax with minute, hour, day-of-month, month, and day-of-week fields. Supports wildcards, ranges, and steps.
Timezone Aware
Each routine carries its own timezone. Schedule nightly jobs in Tokyo time, weekly reports in Berlin time — no UTC gymnastics.
Catch-Up Execution
When the scheduler was down, routines catch up on missed windows bounded by catchUpMax. Never silently skip work.
Overlap Prevention
The scheduler checks for active runs before firing. If the previous window is still running, the new window is skipped automatically.
Run History
Every trigger is recorded with status, timestamps, linked job ID, and error details. Full audit trail per routine.
Manual Trigger
Dispatch any routine on demand via the dashboard or API. Useful for testing schedules before they fire.
How Routines Work
01
Define the Schedule
Set a cron expression, timezone, and optional workflow definition. Configure catch-up max to control backfill behavior.
02
Scheduler Ticks
Every 30 seconds, the scheduler evaluates all enabled routines. When a cron expression matches the current minute, execution begins.
03
Overlap Check
Before creating a run, the scheduler checks for any queued or running execution. If found, the window is safely skipped.
04
Job Dispatched
A routine_run record is created, the linked workflow fires, and the job flows through the standard enrichment → execution → quality gate pipeline.
05
History Recorded
Status, timestamps, job ID, and any errors are stored in routine_runs. The run history is visible on the dashboard and queryable via API.
Related features
Put Your Workflows on Autopilot
Security audits, nightly builds, weekly reports — any workflow, any schedule, with the reliability your team depends on.
Request Early Access