Scheduled scans

Choose a repository and cadencePermalink to Choose a repository and cadence

Use schedules for recurring source assessments, such as a daily review of an actively changing repository or a weekly maintenance review. You need a connected repository in the selected workspace and permission to change schedules. Scanning must also be available, the repository eligible, and quota available when an attempt is due.

There is one schedule per repository. The console offers daily or weekly timing, not an arbitrary recurrence expression. For a one-off scan of a particular branch or ref, use Start a scan and its Branch or ref field.

Create or edit a schedulePermalink to Create or edit a schedule

1. 1

   Open Schedules

   Find the repository and choose Add a schedule, or Edit schedule if one already exists.

2. 2

   Choose daily or weekly

   For weekly scans, also select the day of the week.

3. 3

   Set the UTC time

   Enter the hour and minute. Check the local-time explanation where shown, including any change of weekday.

4. 4

   Enable and save

   Select Run this schedule, then Create schedule or Save schedule. Saving updates this repository's schedule rather than adding a second one.

5. 5

   Check the first attempt

   Return after a due time and read Last run. Open the linked scan when available and inspect its result.

Understand UTC and missed timesPermalink to Understand UTC and missed times

The selected day and time are UTC. For example, weekly Monday at 02:00 means Monday 02:00 UTC, not necessarily Monday 02:00 where you are. The local explanation helps translate the slot; a daylight-saving change can shift your local reading while the UTC schedule stays unchanged.

Pause or remove a schedulePermalink to Pause or remove a schedule

To keep the settings but stop future scheduled attempts, open Edit schedule, clear Run this schedule, and save. Turn it back on and save to resume future attempts. Remove schedule deletes the recurring configuration. Neither action is a substitute for canceling a scan that is already running.

Not scheduled means no schedule is configured. Turned off means the configuration is kept but will not run. A previously successful Last run does not mean a paused schedule is still active, and a next time does not by itself prove that a scan will start.

Interpret Last runPermalink to Interpret Last run