Scheduled scans

A workspace schedule can start a recurring scan, recurring fix reviews of eligible public findings, or both. Instead of starting each run by hand, you set one cadence and choose which actions Apex should trigger using the workspace scope and context you already configured.

Scheduled runs appear in the workspace alongside manual scans and fix reviews, so there is no separate place to look for their results.

• Keep monitoring a workspace continuously instead of remembering to start each scan by hand.
• Catch regressions and newly introduced issues automatically as the code keeps changing.
• Recheck eligible public findings across the workspace scan history without starting each fix review by hand.
• Keep findings fresh on long-lived systems where the security surface shifts over time.

Scheduling is configured from the workspace scan list. The steps below walk through turning on recurring workspace scans, scheduled Fix Review, or both.

1. 1
   Open the workspace

   Go to the workspace you want to monitor and stay on the scan list view.
2. 2
   Open the schedule dialog

   Select Schedule in the scan list header to open the Auto-trigger scans dialog.
3. 3
   Choose what to schedule

   Enable Auto-trigger scan, Auto-trigger fix review, or both. For Fix Review, choose whether each repository should use its workspace/default branch or the same named branch override.
4. 4
   Choose a cadence

   Set the interval with Every and a number, then pick Days or Weeks. Weekly schedules also let you choose the day of the week the schedule runs.
5. 5
   Save the schedule

   Select Save schedule. Apex records the schedule and shows the next run date.

Scheduled Fix Review is for teams that want Apex to revisit known findings after fixes have had time to land. It is narrower than a full workspace scan: Apex verifies eligible existing findings instead of hunting for unrelated new issue classes.

• Scheduled Fix Review preflights public findings from every non-archived, non-fix-review scan in the workspace history, then starts only eligible reviews.
• It is not limited to the latest scan, and it does not create a new workspace scan before checking fixes.
• Workspace branch lets each repository use its default or configured workspace branch.
• A named branch override applies to every repository in the workspace, so use it only when that branch exists across the repository set.
• It consumes Fix Review capacity like manual Fix Review and reports started, reused, skipped, and reconnect-required work in the scheduled-scan run.

The interval is an Every value paired with a unit. Pick the granularity that matches how often the workspace changes and how quickly fixes are expected to land.

• Days: run every N days, up to 365.
• Weeks: run every N weeks, up to 52, on a chosen day of the week.
• The enabled scan and fix-review actions share the same cadence.
• The dialog summarizes the schedule (for example, "Every 2 weeks on Mon") and shows the next run date.

Open the Schedule dialog again at any time to change the cadence, day of the week, fix-review branch, or which actions are enabled. The dialog also shows the next run. Its Last successful value tracks successful Auto-trigger scan starts; fix-review-only runs do not update that value.

Auto-trigger scan and Auto-trigger fix review can be turned off independently. Turn both off and save to stop the schedule while leaving manual scans and fix reviews untouched.