Why can't I see the raw workflow log for my scan?

Why this happens

Every phase of a scan writes readable deliverables and per-agent logs. The full workflow log for any scan sits with the platform administrator. That is by design, and the page does not offer it to workspace users.

Nothing is wrong with your account. Your results are all there.

How to fix it

You rarely need the raw log. Most questions have an answer in places you can open.

1. Start at Recent Scans and click the scan. Its Overview tab shows status, trigger, location, cost, profile and times.
2. Read the live counters for cost, tokens and lines of code while the scan runs.
3. Switch to the Sitemap tab to see what recon found, with a one-line note for each endpoint and a role chip where one applies.
4. Open a finding and read its Evidence tab. It holds the payload, the HTTP request and response, reproduction steps and a screenshot.
5. Check the Activity feed to see who started, cancelled or deleted a scan, and when.

Together these show what a scan did and how it reached each finding, without the low-level detail.

Still not working?

If you need a deeper look at one scan, such as why it ran long or stopped early, send the scan ID and target name through /contact. The eight-character ID is in the page header. Cyberlop can then look into it for you.

For slow runs in particular, read why a scan can take longer than usual first.

Related questions

• What can I see on a scan while it's still running?
• Why is my scan taking much longer than usual?
• How do I see what's been happening in my workspace?
• How do I see the HTTP request and response that proved a finding?
• What does "Scan failed — The scan could not be completed" mean, and what should I do?

Full tutorial

The scan detail page: how to read a Cyberlop scan from Overview to Diff

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre