Troubleshooting Code Vulnerability Scan Failures

Overview

This guide explains how to troubleshoot Code Vulnerability Scans that are partially successful, failed, or manually stopped. You will learn how to:

• Interpret scan status indicators
• Identify failed jobs
• Access and review error logs
• Understand common failure scenarios

---

Prerequisites

• A completed, partially completed, failed, or stopped Code Vulnerability Scan
• Access to the Code Vulnerabilities dashboard

---

Understanding Scan Status

Scan status is displayed using icons in the projects list.

• Completed – All jobs executed successfully
• Partially Completed – At least one job succeeded and at least one job failed
• Failed – All jobs failed
• Stopped – Scan was manually stopped by the user

Hover over the status icon to view the tooltip message for more details.

Icon colors indicate result state. For example:

• Yellow indicates partially completed
• Gray indicates manually stopped

---

Steps to Troubleshoot Failed or Partial Scans

1. Check Overall Scan Status

1. Navigate to Code Vulnerabilities → Projects
2. Locate the scan project
3. Review the Status Icon
4. Hover over the icon to see the status message

If the scan shows partially completed or failed, proceed to review logs.

---

2. Open Scan History

1. Click the project name to open the Findings dashboard
2. Navigate to the History tab
3. Review the list of historical scans for that repository
4. Check the Status column for failed or partial entries

---

3. View Error Logs

1. Open the three-dot menu for the affected scan
2. Click Error
3. Expand error entries using the arrow button
4. Review detailed logs

Only partially successful or failed jobs will display error details.

There may be multiple error logs for a single scan.

---

Common Failure Scenarios

Temporary Processing Issue

Example error message may indicate:

• Temporary internal processing error
• Retry recommended

Action:

• Re-run the scan
• Contact support if the issue persists

These logs do not expose sensitive data.

---

Manually Stopped Scan

If the icon is gray, the scan was stopped by a user before completion.

Action:

• Trigger a new scan using the Run button

---

When to Contact Support

Contact support if:

• Repeated failures occur after retrying
• Authentication errors persist
• Scanner configuration changes do not resolve the issue
• Logs indicate unknown processing errors

Include relevant error log details when submitting a support request.

---

Field Reference

Field	Description	Example
Status Icon	Overall scan result indicator	Completed / Partial / Failed / Stopped
History Tab	Displays all past scan executions	History
Status Column	Shows result of each historical scan	Failed
Three-dot Menu	Access error details	Error
Error Logs	Detailed job failure information	Processing error