Run and schedule scans

Overview

An active engagement scans on its schedule, and you can start a scan on demand at any time. Every run covers the engagement's whole scope. Each engagement runs one scan at a time.

Run a scan on demand

1. In Manage > Engagements, open the row menu (⋮) and click Run scan, or click Run scan in the settings page header.
2. Review the Saved scan configuration (coverage, cadence and location). Click Edit configuration to change it first.
3. Click Reserve and run. The row changes to Queued, then Running, and updates while the scan runs.

• Run scan is offered only on active engagements and is greyed out while a run is in progress.
• The credit figures in the dialog are in preview. See Credits and usage.

Retry, cancel and held runs

A Held run is paused for a reason shown in its status tooltip, for example "Awaiting your approval to proceed." You answer approvals on the Targets page. See Human-in-the-loop approvals.

• An LLM run first checks that the endpoint is reachable and waits out up to 30 minutes of outage before it shows as held.
• A cloud run inventories your resources first. Checks start within an hour either way, and a cloud run has an 8 hour limit.

Set the schedule and scan window

1. Open the engagement's settings and go to the Schedule tab (in the wizard, the Scan Window & Settings step).
2. Under Schedule & Cadence, turn on Scheduled Scan and set how often: every 1 to 365 days, weeks or months. Turn it off to scan on demand only.
3. Choose a Scan Window and a Timezone.
4. Click Save Changes.

• Scheduled starts are spread over the first hour of a window, and a scan starts only when at least 3 hours of the window remain.
• Activating with 24 / 7 starts the first scheduled scan immediately. Any other window waits for the next opening.

Scan calendar

The calendar panel on the Engagements page shows past and upcoming runs for the month. Its header states the month's count.

• Use the arrows to move between months. Each day names up to two engagements, then "+N" for the rest.
• Past runs carry a coloured dot: Succeeded, Warnings, Failed, Running or Other. Projected runs have no dot.
• Click a day to filter the table to that day's engagements. Click the X to clear the filter.
• Projected runs come only from your own cadence and are provisional.

Good to know

• Scheduled runs on an unverified web app domain are skipped. Verify the domain in Engagement settings.
• Pausing stops schedules but lets a run in progress finish. Use Cancel run to stop it.
• The list and settings page refresh automatically while a run is in progress.
• Starting, retrying and cancelling runs needs the Write permission for the engagement's type, for example Engagements > Cloud: Write.