Analysis Stuck or Slow
Troubleshoot analyses that appear stuck, slow, or take longer than expected to complete.
## Analysis Stuck or Slow
Occasionally, an analysis may appear stuck or take longer than expected.
This page explains common reasons and how to resolve them.
---
## What “stuck” usually means
In most cases, the analysis is still running.
Reasons include:
- Large repositories
- First-time baseline analysis
- Dependency or supply chain scanning
- Temporary queue load
The status may not update immediately.
---
## Common causes of slow analysis
### Large or complex repositories
Repositories with many files, large histories, or multiple languages require more processing time.
First-time full analyses are usually the slowest.
---
### Supply chain and dependency checks
Dependency analysis may take longer when:
- Many dependencies exist
- Lock files are large
- External vulnerability data is evaluated
This is expected behavior.
---
### Diff vs full analysis mismatch
Running a full analysis for small changes may be unnecessary.
For pull requests and incremental fixes, diff analysis is faster and recommended.
---
### Queue or system load
During peak usage, analyses may be queued briefly.
Queued analyses will start automatically once resources are available.
---
## How to check analysis progress
- Verify the analysis status indicator
- Refresh the page after a short wait
- Check whether other analyses are running concurrently
Avoid restarting analyses prematurely.
---
## What you can do
If an analysis feels slow:
1. Wait a few minutes and refresh
2. Confirm whether it is a full or diff analysis
3. Reduce scope if possible
4. Avoid running multiple full analyses simultaneously
Patience often resolves the issue.
---
## When to re-run analysis
If an analysis truly stalls:
- Cancel it if the option is available
- Re-run using diff analysis
- Verify repository access and permissions
Repeated stalls may indicate configuration issues.
---
## What not to do
- Do not repeatedly restart analyses
- Do not stack multiple full analyses
- Do not assume failure without confirmation
These actions can increase delays.
---
## When to contact support
Contact support if:
- The analysis remains stuck for an extended period
- Errors are reported in the UI
- Results never appear after completion
Provide the project name and analysis ID if available.
---
## Next steps
- Empty or missing results
- Permission and access errors
- General FAQ