#036Guide3 min

What to do when an analysis is partial

Identify what stopped, keep the useful evidence, and complete the missing checks without confusing partial coverage with a clean result.

Hackaiz team · updated 21/11/2026

Illustration: a team reads a security report and marks priorities.
Illustration: a team reads a security report and marks priorities. Illustrative photo, not a screenshot.

01Read the status before the findings

A report marked ‘Partial scan’ contains work that did not cover the whole intended scope. It is not the same as ‘Scan completed’, and it should not be read as a successful examination of every connected system. Start with the status and the explanation shown for that analysis, rather than jumping straight to its finding count.

Distinguish this from ‘Scan interrupted’. For an interrupted scan where no check could complete, the screen says that no result is reliable and asks you to fix the cause before scanning again. A partial report can still provide useful evidence from completed work. Keep those observations, but leave any unexamined area explicitly unresolved.

02Identify the blocker, not just the symptom

The documentation describes several reasons for incomplete work: credits may have run out, access to a repository or database may be missing, or checks may have been unticked. These require different responses. Purchasing credits does not repair a permission error; reconnecting a repository does not automatically examine a database that was never connected.

For example, a repository check may produce code findings while the database remains unexamined. Do not discard the code evidence, and do not conclude that database access rules are correct. Write down the missing system and the reason shown. If a check was deliberately excluded, decide whether that exclusion still fits the question you need the analysis to answer.

03Complete the missing work deliberately

Each analysis uses credits. Unticked checks are neither run nor billed, so turning a check off is a scope decision, not a way to obtain its result at no cost. Review your selection and available access before requesting more work. For websites and APIs, domain ownership proof is required before analysis: DNS TXT at _hackaiz, the HTTPS verification file, or asking the project’s AI to create that file.

  1. 1Read the cause displayed beside the unfinished analysis and list the checks still missing.
  2. 2If credits ran out, use the pause banner to obtain credits; continue only where the scan offers a continuation option.
  3. 3If access is missing, connect the relevant system or correct its permissions, then review the selected checks.
  4. 4Under Your next actions, use Partial analysis: finish checking the rest when that option is present.

04Keep the boundary visible when you resume

Continuation can use the last saved point when it remains valid; otherwise a new analysis is needed. Do not promise colleagues that every partial run can resume exactly where it stopped. After continuation or a new run, check the status again and confirm that the previously missing work now has an actual result, rather than merely a connection.

If a completed part already reports a serious issue, investigate it while you restore coverage elsewhere. In a handover, separate ‘evidence available’ from ‘checks still outstanding’. Include the target and the analysis you are referring to. This avoids delaying an urgent correction simply because another system could not be examined, while preventing an unfinished report from being presented as clearance.

Frequently asked questions

Was this article helpful?

Related articles