Missing Results

Troubleshoot missing or incomplete scan results.

---

Scan Shows No Vulnerabilities

Is This Actually a Problem?

No vulnerabilities might mean:

• Your code is secure (good news!)
• Scanners didn't find issues
• Quick preset used (fewer scanners)

Verify Scan Completed

Check scan status:

• Status should be "Completed"
• Duration should be reasonable
• All selected scanners ran

Check Which Scanners Ran

Different presets use different scanners:

Preset	Scanners
Quick	3 (Slither, Solhint, Aderyn)
Standard	5-7 (+ Semgrep, Wake)
Deep	10+ (+ Mythril, Echidna)

Try a more thorough preset for more coverage.

---

Some Files Not Scanned

Check Upload Contents

Verify all files were included:

# List archive contents
unzip -l project.zip

# Check specific file
unzip -l project.zip | grep Token.sol

File Extension Check

Only these extensions are scanned:

• .sol - Solidity
• .vy - Vyper
• .rs - Rust

Other files are ignored.

Path Issues

Files must be accessible:

• Not in excluded paths
• Valid import paths
• Correct file structure

---

Scanner Didn't Find Expected Issue

Scanner Limitations

Each scanner has different capabilities:

Scanner	Strengths	May Miss
Slither	Fast, comprehensive	Complex logic bugs
Mythril	Deep symbolic	Time-limited paths
Echidna	Invariants	Without properties

Known Detection Patterns

Check if your issue type is detectable:

• Reentrancy - Slither, Mythril
• Access control - Slither, Aderyn
• Integer overflow - Slither (pre-0.8)
• Logic bugs - Echidna (with properties)

Add Test Properties

For fuzzing detection, add properties:

function echidna_balance_invariant() public view returns (bool) {
    return address(this).balance >= minBalance;
}

---

Results Disappeared

Check Retention Period

Results are retained:

• Default: 1 year
• Configurable for Enterprise

Old results may have been purged.

Check Correct Organization

Ensure you're viewing correct org:

• Click organization selector
• Verify you're in right context
• Check project access

Check Filters

Clear any active filters:

• Severity filter
• Date range
• Scanner filter
• Status filter

---

Partial Scanner Results

Individual Scanner Timeout

One scanner may timeout while others complete:

• Check scanner status in results
• Some may show "Timed out"
• Other results still valid

Scanner Errors

Check for scanner-specific errors:

• Expand scanner section
• Look for error messages
• May indicate code issues

Re-run Specific Scanner

Try re-scanning with different settings:

1. Use Custom scanner selection
2. Increase timeout (Enterprise)
3. Simplify code complexity

---

Deduplication Questions

"Where Did Findings Go?"

BlockSecOps deduplicates across scanners:

• Multiple scanners may find same issue
• Shown once with sources listed
• Expand to see all scanner details

Check "All Findings" View

Toggle deduplication:

1. Go to scan results
2. Click "Show All" or disable grouping
3. View individual scanner findings

---

Low Risk Score

Understanding Risk Scores

Risk score factors:

• Severity (Critical > High > Medium > Low)
• Confidence level
• Exploitability
• Context

A low score doesn't mean "not important."

Review Low Scores Too

Even low-scored findings may matter:

• Code quality issues
• Best practice violations
• Potential future risks

---

Export Issues

Export Missing Data

If export seems incomplete:

1. Check export format (JSON has most detail)
2. Verify all sections selected
3. Try different format

Large Export Timeout

For large result sets:

• Filter before export
• Export in sections
• Contact support for bulk export

---

Troubleshooting Checklist

1. Scan status - Is it "Completed"?
2. Preset used - Was it thorough enough?
3. Files uploaded - All contracts included?
4. Dependencies - Were they included?
5. Filters - Are any hiding results?
6. Organization - Correct context?
7. Retention - Within retention period?

---

Comparing to Other Tools

Different Results from Local Slither

BlockSecOps may show different results due to:

• Version differences
• Configuration differences
• Dependency resolution
• Deduplication

Missing Issues Found Elsewhere

If another tool finds something BlockSecOps misses:

1. Report to support
2. Provide sample code
3. Help improve detection

---

When to Contact Support

Contact support if:

• Scan completed but dashboard is empty
• Known vulnerability not detected
• Results disappeared unexpectedly
• Export is corrupted

Provide:

• Scan ID
• Expected vs actual results
• Contract details
• Other tool results (if applicable)

See Contact Support.