Why did my scan fail, skip, or complete with errors?

Use this article when a scan fails, is skipped, is aborted, is cancelled, or completes with errors.

What to check first

• Open the Scans view and find the affected scan.
• Read the Status column for the lifecycle state.
• Read the Result column for the reported outcome.
• Check whether the same repository or ref has repeated failures.

Common terminal statuses

• Completed with Errors: the scan finished, but some non-blocking work failed.
• Failed: the scan encountered an error and could not complete normally.
• Skipped: the scan did not run because conditions or limits prevented it.
• Aborted: the scan stopped before completion.
• Cancelled - No SWUs: the scan stopped because the Shift Work Units balance was insufficient.

Unavailable Go dependency inventory

If a Go dependency graph cannot be generated, Cysmiq reports the SBOM as unavailable and preserves previously known package data. The affected pull request assessment becomes unavailable, and its check finishes without blocking. Check dependency access and scan details before treating the inventory as complete. Contact support with the scan ID if this repeats.

What to do next

• If Rescan appears in the scan action menu, select it to retry the eligible failed scan for the current ref head.
• If Rescan is absent, the repository may be inactive, the failed scan may no longer represent the current ref head, or another scan may already have replaced it.
• If the scan completed with errors once, check whether later scans on the same repository complete normally.
• If scans repeatedly fail or skip, collect the repository, ref, scan ID, and approximate time before contacting support.
• If a scan was cancelled because of SWUs, review your plan or available balance with your workspace administrator.

Canonical docs

For the maintained reference, see Dependencies, Scans, and Scan drill-down actions.

Contact support if

• The same repository repeatedly fails, skips, or completes with errors.
• A scan appears stuck after a terminal status was expected.
• You expect Rescan to be available after confirming the repository and ref are current.
• You need help interpreting a scan status, result, or VCS status check.