Auto-Runs & Triggers

Automatically start more comparison Runs when models or prices change.

New Monitors start with automation off. After the first manual Run, configure triggers on the Monitor's schedule panel.

• Weekly — the standing heartbeat
• Catalog — a new model enters the candidate policy
• Price — a candidate list price changes
• Drift — production traffic no longer resembles the previous corpus
• Deploy — Prompt CI tests a prompt change on every paid plan

Scheduled triggers are debounced to avoid duplicate daily work. Deploy Runs deliberately bypass that debounce because several prompt changes in one day are separate CI events. Every started trigger uses one organization-pooled Run. A per-Monitor automation cap is a safety rail, not additional plan capacity.