Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Running scans

Running scans

How do I cancel a running scan?

Quick answer

Cancelling needs the scan:cancel permission. The API call is POST /api/scans/:id/cancel, and the scan then ends as Cancelled. The captured scan list shows Scan, Report and delete actions only, so ask your admin or use the API.

Steps

Cancelling stops a run that is still going. You may want this after starting the wrong profile.

  1. Check your permission. You need scan:cancel. Ask an admin if unsure.
  2. Copy the scan ID. Open the scan; its ID is in the page address.
  3. Send the cancel call. POST to /api/scans/:id/cancel with your session or Bearer API token.
  4. Refresh the page. Click Refresh on the scan detail page.
  5. Confirm the result. The row should show Cancelled.

Good to know

The Recent Scans table offers Scan, Report and a trash icon. A cancel control did not appear in that list when we captured it. Still, the reference lists the call: POST /api/scans/:id/cancel, which cancels a running scan and needs scan:cancel.

Calls work with a session cookie or a Bearer API token, and an admin issues the tokens. If you cannot make the call yourself, ask your admin or write to /contact with the scan ID.

The Activity page records a Cancel · Scan entry, so you can confirm who cancelled and when. Cancelled runs show a grey Cancelled badge in Recent Scans.

After you cancel

Findings found before the stop can still appear on the scan, in the same way a failed scan can still hold findings. Start a new run when you are ready. A cancelled run cannot be resumed, so a fresh run starts from the beginning of the pipeline.

Keep the scan ID handy, because the address of the scan detail page ends with it and the API call needs it. If you work from a pipeline, the same cancel call works there with an API token that holds the right permission. Plan ahead.

Full tutorial

Failed or cancelled scans: what to check and how to re-run

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.