Managing scan execution

Scan History (in the sidebar) lists every scan of the team, newest first and grouped by day, with what it ran, what it changed and what it cost. Click a scan's time or target to open its page, where you follow a running scan and see what a finished one changed; see The scan page. New Scan at the top opens the Static Code Analysis form.

zoom_inEnlarge

At the top of the page

• Running now · N shows a card for each scan in progress: its stage and progress where the scan reports them (Stage N of M: <stage> (done/total), for AI SAST and AI Pentest), how long it has run, what it has cost and its product, with a button to stop it. Show all N lists them all when there are more cards than fit.
• The tiles count the scans of the chosen period, those Running or queued and those that Failed (click either to filter the list), the findings the scans reported first and closed (Findings new / fixed), and the LLM spend.
• When scans start after the page was opened, a banner says so; Show them reloads the list. When a scan ends, a notice in the corner says Scan <target> finished., failed. Open it to see why. or was cancelled.

Filtering

The list shows the Last 30 days by default. Above it you can:

• search by target, branch, commit or scan ID (product names, scan types and statuses match too);
• choose the Period (the last 24 hours, 7, 30 or 90 days, all time, or a custom range), the Product, the Scan type and the Status (Running or queued, Finished, Failed, Cancelled);
• open More filters for a single Target of the chosen product, the Mode, the From and To dates of a custom range, how the scan was started (Started via: Manually, Schedule, Repository monitor, Rerun or AI resume), who started it (Started by), and Only scans that changed findings.

Each active filter shows as a chip you can remove; Clear filters removes them all. The filters are kept in the page address, so a filtered list can be bookmarked or shared. When older scans fall outside the period, the page says how many and offers Show all time. The footer reads Showing x to y of N results, with the page links. To search across assets, vulnerabilities, scans and credentials at once, use Global search and activity log.

Reading the list

Scans shows one row per scan:

By target switches to one row per target:

Controlling scans

Scan outcomes

A scan can end without covering everything it was given. The scan's page and its log say which case applies:

For a CI job, a target that was unreachable is not a failure: the gate decides on what the reachable targets returned. See CI/CD and automation.

Acting on several scans

Tick scans to act on several at once. When every scan on the page is ticked, you can also select all the scans the filters match.

• Stop selected stops the running ones.
• Rerun selected runs each ended scan again with its own settings, up to 50 at a time; running scans are skipped.
• Download reports downloads one ZIP holding each scan's report as <scan id>-report.zip, up to 200 scans at a time.
• Delete selected deletes the records of ended scans; running scans are left alone.

Export CSV downloads every scan the filters list, one row each: when it started and ended, its type, mode, target, product, status, how and by whom it was started, the branch and commit, what it changed and what it cost. The export is recorded in the team's activity log.

Clear History deletes every scan record of the team, after a confirmation.