Schedules
Create a schedule on the Schedule step of the scan wizard.
| Option | Runs |
|---|---|
| Run now | Once, immediately. |
| Later | At the chosen date and time, then again on that date each year. |
| Repeat | Daily, weekly, monthly, or on a cron expression. A cron schedule can run at most every 15 minutes. |
A scheduled web or API scan can use only a saved authentication profile. Session secrets typed into the wizard are not stored on a schedule.
Manage schedules
Section titled “Manage schedules”The console creates schedules. To rename a schedule, change its target, cron expression, time zone or enabled state, or run it immediately, use the API at /api/schedules. See REST API.
When a scheduled run does not start
Section titled “When a scheduled run does not start”Each schedule records the outcome of its last attempt.
| Situation | Outcome |
|---|---|
| The previous run is still active | Skipped. |
| No capacity on the host | Skipped. |
| An update is in progress | Waits for the update. |
| The scan is refused | Not started. The reason is audited and a Scheduled scan did not start notification is raised. The schedule stays enabled. |
| The creator is disabled, loses project access or becomes a viewer | The schedule is disabled. |
| The cron expression has no future run | The schedule is disabled. |
A scan that starts and then fails is shown on its own scan page.