Why does my failed scan still show findings?

Why this happens

Findings are saved as the scan works, not only at the end. When a run stops early, the red banner appears, yet the findings that were already recorded stay on the scan. On a failed scan we captured, the tabs read Findings (43) and Sitemap (34).

So the result badge tells you how the run ended, and it says nothing about whether the list is empty or wrong, which is why a red badge can sit beside a long and useful list.

How to fix it

Nothing is broken. You only need to decide how to use the partial list.

1. Open the scan and click the Findings tab.
2. Read each row as you would on a completed scan. Click a row to open the evidence.
3. Triage what you can already judge: set a disposition, add an assignee and click Update status.
4. Remember that the list is partial. Phases that never ran could not add anything.
5. Press Scan on the profile to get a full run, then compare the two with the Diff tab.

Note that the Report button in the scan list shows only on completed scans. To pull partial findings out, use Export JSON or Export CSV on the Issues page instead.

Still not working?

• If the Findings tab is empty, the scan stopped before it found anything. Re-run it.
• If the banner keeps coming back, read what the failed banner means.
• Findings persist per target across scans, so a later full run updates the same issues rather than starting over.
• For anything else, use /contact.

Related questions

• What does "Scan failed — The scan could not be completed" mean, and what should I do?
• What do Completed, Failed and Cancelled mean on a scan?
• How do I compare a scan with the previous one?
• How do I export findings as JSON?
• How do I re-run a previous scan?

Full tutorial

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

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre