> ## Documentation Index
> Fetch the complete documentation index at: https://docs.codethreat.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scan Problems

> Troubleshooting scan-related issues

Detailed troubleshooting for scanning issues.

## Scan Won't Start

### Stuck in PENDING

**Possible causes**:

* Queue backlog
* Plan scan limit reached
* Worker availability

**Solutions**:

1. **Check plan usage**:
   * **Settings** → **Billing** → **Usage**
   * Verify you haven't hit monthly scan limit

2. **Wait for queue**:
   * Scans typically start within 5 minutes
   * During peak times, may take up to 10 minutes

3. **Cancel and retry**:
   * Cancel pending scan
   * Start new scan

4. **Contact support**:
   * If pending >15 minutes, contact support with scan ID

## Scan Failures

### Repository Access Errors

**Error**: "Failed to access repository"

**Causes**:

* VCS token expired
* Repository deleted/archived
* Permissions revoked

**Solutions**:

* Reconnect VCS integration
* Verify repository exists and isn't archived
* Check access permissions

### Timeout Errors

**Error**: "Scan timed out"

**Causes**:

* Repository too large
* Too many files
* Deep Git history

**Solutions**:

* Exclude large directories (node\_modules, vendor)
* Reduce files scanned with `.codethreatignore`
* Contact support for large repo optimization

### Out of Memory

**Error**: "Scan failed: out of memory"

**Causes**:

* Very large files
* Too many dependencies
* Complex analysis

**Solutions**:

* Exclude generated files
* Split monorepo into smaller repos
* Contact support

## Incomplete Results

### Missing Violations

**Symptoms**: Expected violations not appearing

**Possible reasons**:

* AI filtered as false positive
* File/directory excluded
* Language not supported
* Insufficient rules coverage

**Check**:

1. Review AI-filtered violations
2. Check scan configuration exclusions
3. Verify language support
4. Contact support if issue persists

### Wrong Severity

**Symptoms**: Violation severity seems incorrect

**Explanation**:

* CVSS score determines severity
* EPSS score influences priority
* Severity can be overridden in enterprise plans

**Action**:

* Review CVSS/EPSS scores
* Provide feedback if genuinely incorrect

## Performance Issues

[View detailed scan performance optimization →](/scanning/scan-types#scan-performance)

## What's Next?

<CardGroup cols={2}>
  <Card title="Common Issues" icon="circle-question" href="/troubleshooting/common-issues">
    Back to common issues
  </Card>

  <Card title="Integration Issues" icon="plug" href="/troubleshooting/integration-issues">
    VCS integration problems
  </Card>
</CardGroup>