Skip to main contentDetailed troubleshooting for scanning issues.
Scan Won’t Start
Stuck in PENDING
Possible causes:
- Queue backlog
- Plan scan limit reached
- Worker availability
Solutions:
-
Check plan usage:
- Settings → Billing → Usage
- Verify you haven’t hit monthly scan limit
-
Wait for queue:
- Scans typically start within 5 minutes
- During peak times, may take up to 10 minutes
-
Cancel and retry:
- Cancel pending scan
- Start new scan
-
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:
- Review AI-filtered violations
- Check scan configuration exclusions
- Verify language support
- 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
View detailed scan performance optimization →
What’s Next?
