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 / Getting started

Getting started

Why does the Cost column on the Dashboard show a dash for some scans?

Quick answer

A dash in the Cost column means the scan has no cost to show. On the Dashboard it appeared on scans that failed early. Open the scan row and read the Cost field on the Overview tab. If a Failed scan keeps repeating, contact us.

Why this happens

The Cost column in Recent scans shows a dash when there is no cost to report. The page does not explain the cause. In the sample view of the app, the dashes sat on two Failed scans that started a minute apart. Completed and Cancelled scans showed an amount.

So a dash most likely means the run stopped before it spent anything. It is not a billing error.

How to fix it

  1. Find the scan in Recent scans on the Dashboard. Note its Status.
  2. Click the row to open the scan page, where you will see the Overview tab first.
  3. On the Overview tab, read the run details: Status, Trigger, Location, Cost, Started and Finished.
  4. If the scan Failed, read the red banner. It tells you to try again and to contact your administrator if the problem persists.
  5. Click Scan on the row in Recent Scans to run it again.

Still not working?

  • A Failed scan can still hold findings found before it stopped. Open the Findings tab.
  • Check Settings → AI Provider and Settings → Plan & usage. When you use up the included AI allowance, scans on it pause until next month. You can connect your own key to continue.
  • For a private repository, check that you have saved a Git token. See how to scan a private repository.

You cannot remove a dash by changing settings, and you do not need to. It tells you that no cost came out of that run, which is useful when you compare costs between scans, because you would not want to call a failed run a cheap one.

Only the platform administrator can read the low-level run log. If the same scan fails again, contact us with the target name and the time it started.

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.