Scheduled monitoring and refreshes
Scheduled monitoring and refreshes: why scheduled monitoring is included in your plan and how it differs from refreshes.
Scheduled monitoring is included
Scheduled monitoring is part of your plan. The runs a schedule starts never use your refresh allowance, so you can leave your schedules running without watching a meter. How often they run is set by the cadence, not by a quota: a daily schedule runs once a day, a weekly one once a week.
The cadence your plan allows is the main lever: most paid plans monitor daily, and some plans monitor weekly. What each run covers (your prompts across the assistants you have enabled) stays the same.
How this differs from refreshes
Refreshes are for manual runs you start yourself between scheduled runs (for example, Refresh now after you publish a change). Those draw on your monthly refresh allowance. Scheduled runs do not. So even if you are out of refreshes, your scheduled monitoring keeps going.
For what a refresh is and how the allowance works, see Refreshes and how runs are billed.
More than one schedule per project
You can add several schedules to a project (for example a weekly check plus a monthly deep look), up to the number included in your plan. Each one runs on its own cadence.
Failed runs don't count
A run that fails or is cancelled does not count and costs nothing.
Changing plans
If you move to a smaller plan, any schedules over the new plan's per-project limit are paused (the oldest ones stay active), and any schedule set more often than your new plan allows is dialled back to the fastest cadence it does allow. Nothing is deleted, and you can turn schedules back on or speed them up again if you upgrade.
Busy times
At busy moments a run can wait a few minutes in a queue before it starts. You will see a note on the scan page while it waits, and it keeps running even if you close the tab.
For how to set schedules up and choose alerts, see Scheduling scans and email alerts.