Skip to main content
Every Octopoda scan has a status, a time limit and a credit cost. This page explains what you see on the Scans page in the web app and in octopoda status, and what happens to your credits when a scan does not finish.

​
Kinds of scan

Most code scans finish in 10 to 30 minutes. Credits are taken when the scan is created.

​
Statuses

See How Octopoda works for the stages a running scan goes through.

​
Refunds

If a scan fails because of a problem on our side, its credits are refunded automatically and the scan page says so. To run it again, select Run again on the scan page for a repository scan, or run octopoda scan again for a scan you started from the CLI. If a scan fails because of the code itself, for example an upload that could not be unpacked, the scan page shows the reason and the credits are not refunded.

​
Cancel a scan

Open the scan in the web app and select Cancel scan. A scan that was still queued is cancelled at once. A running scan stops shortly after.

​
Find a scan

The Scans page lists every scan in the account. Filter by Status, Repository or Trigger: PR (a pull request check), Dashboard (the web app), CLI or AI tool (the MCP server). From the CLI, octopoda status shows your latest scan, and octopoda status <scan id> shows a specific one.

​
Emails

When a scan you started from the CLI, the MCP server or the web app finishes, Octopoda emails you a one-line summary. Pull request scans report on GitHub instead. You can turn these emails off in Notifications.