Scan statuses, time limits and refunds

What each Octopoda scan status means, how long each kind of scan may run, how the queue works, and when the credits for a scan are refunded.

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

Kind	Started by	Credits	Time limit
Pull request scan	A pull request on GitHub, when checks are on	1	20 minutes
Code scan	The CLI, the MCP server or New scan in the web app	5	30 minutes

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

​

Statuses

Status	Meaning
Queued	Waiting for a free slot. Your plan sets how many scans run at the same time (1 on Builder, 2 on Pro, 5 on Team). The scan starts when one of your running scans finishes.
Starting	Octopoda is starting the private sandbox.
Running	The scan is under way. The page shows the current stage, the activity, and findings as soon as they are proven.
Complete	The scan finished.
Partial	The scan reached its limit before it finished. Its findings are proven, but parts of the app may not have been tested.
Failed	The scan could not finish. The scan page says why.
Cancelled	The scan was stopped.

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.