Skip to main content
A scheduled scan runs a deep scan on a recurring cadence, so your findings stay current as the code changes. Each run scans the head commit of the scheduled branch at that moment.

Create a schedule

Open a repository and click Schedule, or go to the repository’s Settings tab and use Scheduled Scans. Then choose:
1

Repositories

  • All repositories: one schedule per repository.
  • Selected: one schedule for each repository you pick.
  • Multi-repo: one grouped schedule that scans the selected repositories together as a single multi-repo scan. All of them must use the same provider, so create one schedule per provider. A public API request that mixes GitHub and GitLab fails with 400 mixed_repository_providers.
2

Branch

Each schedule scans one branch. Leave it empty to scan the default branch. To scan two branches of a repository, create two schedules.
3

Cadence

In Basic mode, pick Daily, Weekly (the default), or Monthly. Use Cron mode for a custom schedule. A schedule runs at most once a day.

What each run does

Each run is an ordinary deep scan:
  • Issues already tracked update their existing finding instead of creating a duplicate.
  • A Fixed finding that is detected again is reopened.
  • With fix detection on, open findings whose code has been fixed are marked Fixed.
Scheduled scans of the default branch are the simplest way to keep fix detection working without anyone remembering to re-scan.

Choosing a cadence

Pair scheduled scans (full-codebase coverage over time) with PR checks (catch issues before merge). Route results with Slack or your issue tracker.