Scheduled scans

Use scheduled scans to confirm monitoring entitlement, accepted scope, next_scan_at and run links before interpreting recurring issue changes.

Customers, agencies and developers

Feature availability

Product, package, provider and deployment boundaries for this page.

Available from
Current documentation
Deployment modes
cloudself-hosted

Before scheduled monitoring

Use this page after the project has accepted scope, a completed baseline scan and an active Monitor Plan. Scheduled scans are recurring runs that compare the same accepted scope over time. Do not interpret issue changes until the scheduled run completed and stayed inside the accepted project boundary.

Review scheduled scan state

Follow the path `Monitoring plan → Project monitoring → Scheduled scan → Scan run → Fingerprint comparison`.

  1. Open /billing and confirm the Monitor Plan is active for the same account. Result: recurring scans are tied to provider-confirmed subscription state.
  2. Open /projects/{project}/monitoring after accepted scope and a baseline scan exist. Result: monitoring status, schedule state and project scope are visible before recurring checks start.
  3. Review monitoring_frequency, next_scan_at, last run and schedule state. Result: you know when the next automated scan should run and what baseline it will compare against.
  4. Wait for or open the completed scheduled scan run link when it appears. Result: the run can be inspected before issue changes are trusted.
  5. Confirm the completed run stayed inside accepted scope. Result: recurring evidence does not include unrelated pages or unsupported targets.
  6. Continue to fingerprint comparison after a scheduled run completes. Result: new, recurring and resolved issue states are based on comparable evidence.

Scheduled scan states

Use the schedule state before acting on monitoring evidence.

  • Scheduled means next_scan_at and monitoring_frequency are set for the project.
  • Running means a recurring scan is in progress and issue changes are not ready yet.
  • Completed means the run link is ready and can be compared with the baseline.
  • Paused means subscription, plan, scope or project state is blocking recurring runs.

Blocked or unavailable states

Do not work around a blocked monitoring state.

  • Monitoring plan required means choose an available Monitor Plan before expecting recurring scans.
  • Baseline scan required means complete the first live audit before recurring comparison.
  • Accepted scope missing means return to accepted scan scope before scheduled runs continue.
  • Past due subscription means scheduled runs can pause until billing state recovers.
  • Scope blocked means remove unsupported or unrelated targets before monitoring resumes.

Continue to comparison

Continue with the related Fingerprint comparison page after a scheduled scan completes. Use the related Issue change states and Monthly summaries pages after comparison explains what changed.

Related documentation

Was this page helpful?

Feedback goes into the product documentation review queue.