Schedule the scan
Schedule web, infrastructure and static scans, manage them on the Schedules page, or schedule from your CI system.
Save a scan to run later, once or repeatedly, and manage every schedule on the Schedules page. Scheduling is done in the web console only: ScanSuite schedules have no API or command. To scan on a timetable from your CI system instead, see Schedule from your CI system.
Creating and changing schedules needs the Operator or Team admin role; Readers only see them.
Web and infrastructure scans
On the Dynamic Analysis page (Web App Scanning) and the Infrastructure page (Infrastructure Checks), the schedule is set in the Schedule & Access (or Schedule & Network Options) section.
- 01Choose the product
Product / Eng ID.
- 02Enter the targets and choose the scanners
As for a scan you run now, see Web App Scanning or Infrastructure Checks.
- 03Choose the Frequency
Once, Daily, Weekly or Monthly. Run or save switches to Save scan, and the start button reads Schedule Scan.
- 04Pick the Date in the calendar
Select the field and choose the day in the date picker. A typed date is read month first, mm/dd/yyyy. The date sets the first run, and the weekday or day of the month it repeats on. A Once scan needs a Date.
- 05Choose the Time
00:30 to 23:30 in half-hour steps, in the ScanSuite server's time zone.
- 06Select Schedule Scan
Scan submitted appears and the form reloads empty. No scan starts now.
- 07Check it on the Schedules page
Select Schedules in the sidebar. The new row shows the product and the save time as its name, the frequency and time under Runs, and the first run under Next run.
Date and time rules
| Rule | What happens |
|---|---|
| Date | The day of the first run, mm/dd/yyyy (month first, as the calendar writes it). A Weekly scan repeats on that weekday, a Monthly scan on that day of the month (day 31 skips shorter months). Pick it in the calendar. |
| Date in another format | Refused with Invalid date. Pick it in the calendar (mm/dd/yyyy) and choose a Time. |
| Time | The time of every run, 00:30 to 23:30 in half-hour steps, in the server's time zone. There is no 00:00. |
| Date in the past | Refused with Date and time should be in future. A date of today with a time already past is refused too. |
| Date left empty | The scan is saved from the moment you select Schedule Scan, and the Time is ignored: a Daily scan runs at the current time of day, a Weekly one on today's weekday. A Once scan is refused with A scan saved to run once needs a Date: pick one in the calendar. |
| Changing Frequency, Date or Time | Switches Run or save to Save scan. To run now instead, set Run or save back to Run now. |
Check: on the Schedules page, Next run shows the date and time you expect. A dash means the schedule will not run (a Once scan saved without a Date by an earlier release); delete it and save it again with a Date.
Change or delete a saved scan
- Choose it in Saved Scans at the top of its scan form. The list shows only the scans you saved. The form fills in and Run or save switches to Save scan.
- Change the targets, scanners or timing and select Schedule Scan. A name you gave on the Schedules page is kept.
- The bin next to Saved Scans deletes the selected scan (Scheduled scan deleted). Scans it already ran stay in Scan History.
Static analysis
On the Static Code Analysis form, Scanning Mode has a Repeat group:
| Option | What it does |
|---|---|
| Daily | Scans now, then every day at Run at. |
| Weekly | Scans now, then every week on today's weekday at Run at. |
| Monthly | Scans now, then every month on today's day of the month at Run at. |
| Run at | The time of the repeat runs, any HH:MM, in the server's time zone. Left empty, the current time is used. |
These modes need a Git repository (an uploaded archive can only be scanned once) and one repository per schedule. Select Start Analysis to save the schedule and start the first scan; then check the row on the Schedules page. Monitor Changes, which scans a branch whenever it changes, is described in Monitored branches and incremental scans.
The Schedules page
Select Schedules in the sidebar to see every recurring scan and repository monitor on one page, Schedules & Monitors: when each runs next and how the last one went. New schedule opens the Static Code Analysis form. With nothing scheduled it reads No schedules yet.
| Column | What it shows |
|---|---|
| Name | The schedule's name, its scan type and product; team admins also see who created it. A new schedule is named after its product and the time it was saved until you rename it. |
| Target | What it scans; for a monitor, also the branch and the last commit it scanned. |
| Runs | Once, Daily, Weekly or Monthly with the time (and the weekday, day of the month or date), or Watches the branch hourly for a monitor. |
| Next run | When it runs next, or Paused. A dash means it will not run again. For a monitor, also when it last checked the branch. |
| Last scan | The latest scan of the same target, product and type, whoever started it, and how it ended (for a monitor, its own last scan). Click it to open the scan. |
| Action | What it does | Who can |
|---|---|---|
| Run now | Asks Start this scan now, in addition to its schedule?, then starts it as you. Offers Open the scan, or says the scan is queued. | Operator, Team admin |
| Pause / Resume | Stops the schedule until resumed. A paused row shows Paused under Next run. | Operator, Team admin |
| Rename | Changes the name. The name survives later saves from the scan form. | Operator, Team admin |
| Delete | Asks first, then removes the schedule. Scans it already ran stay in Scan History. | Operator, Team admin |
Changes take effect within a minute. Members see the schedules they created; team admins see every schedule of their team. An old Incremental Scan entry shows Not scheduled: it no longer runs, so delete it. A product's schedules are also listed on the Scans & schedules tab of its page, see The product page.
In ScanSuite Teams, saved schedules run as the team's scheduler service account, so they keep running after their author leaves the team.
Schedule from your CI system
ScanSuite schedules can only be created in the console. To keep the schedule with your code, or to let an agent set it up, use your CI system's own scheduler to run scansuite-ci, for example a GitLab pipeline schedule (Build → Pipeline schedules) that runs a full scan of the default branch every week. The job and its token are described in CI/CD and automation and GitLab CI step by step.
A person creates the ScanSuite API token and stores it as a masked CI/CD variable (SCANSUITE_TOKEN).
Never paste the token into a chat with an agent.
Using https://scansuite.eu/documentation/usage/schedule-the-scan and https://scansuite.eu/documentation/reference/cicd, add a job to this repository's .gitlab-ci.yml that runs scansuite-ci with --profile full-ai on the default branch only when $CI_PIPELINE_SOURCE is "schedule", and tell me how to create a weekly pipeline schedule (Build > Pipeline schedules, Sunday 02:00) for it. ScanSuite schedules have no API, so use the GitLab schedule. The job reads SCANSUITE_URL, SCANSUITE_TEAM, SCANSUITE_PRODUCT and SCANSUITE_TOKEN from CI/CD variables; do not ask me for the token or any password, and stop and tell me which variables I must add myself. End with how I check that the first scheduled pipeline ran and its scan appears in ScanSuite Scan History.Paste it into Claude Code or another coding agent. See Working with AI agents.
Last reviewed 2026-10-19