01
1. Pick a cadence
- Open /runs/schedules → New schedule. Name it after the asset + intent (e.g. acme-prod-canary).
- Choose cadence: every_hours (1-720), daily (HH:MM), or weekly (dayOfWeek + HH:MM). Match this to your release cycle.
- Paste the RunRequest body (or copy it from a previous one-off run that worked end-to-end).
02
2. Verify the first tick
- The scheduler loop ticks every 60 seconds. Watch /runs?status=queued to see the first run appear at your cadence boundary.
- Pair with a webhook subscribing to run.completed so the tick result feeds your SOC tool hands-off.
- If a deep+high+agentic run overruns the window, the next tick fires only after termination — verify by inspecting last_triggered_at.