Why is my scan taking much longer than usual?

Why this happens

A typical scan of a small app takes roughly an hour. That figure is a guide, not a promise, and three things can stretch it.

• Rate limits. The AI provider can limit requests. Cyberlop waits and retries, even through multi-hour rate windows.
• Size. More code and more endpoints mean more work for every phase, from the first read of the repository to the final report.
• Allowance. When the included Cyberlop AI allowance is used, scans on Cyberlop AI pause until next month.

How to fix it

1. Open the scan from Recent Scans and check the current phase and the live counters.
2. Press Refresh. Moving cost or token numbers mean the scan is working.
3. Go to Settings → Plan & usage and look at the Cyberlop AI bar.
4. Allowance spent? Connect your own key under Settings → AI Provider to keep going.
5. Compare with earlier scans of the same profile, because their Started and Finished times show what is normal for your app.

Do not cancel a scan just because it is slow. A cancelled run keeps what it found, but you lose the rest of the analysis and must start the whole run again.

Still not working?

Still stuck? If a scan makes no visible progress for a long time and the allowance is fine, contact Cyberlop at /contact. Give the scan ID from the header. The raw workflow log is reserved for the platform administrator, so support is the right route for a deeper look.

For the usual timings, read how long a scan takes.

Related questions

• How long does a scan take?
• What can I see on a scan while it's still running?
• Can a long analysis get cut off part-way?
• Where can I see my plan limits and usage?
• Why can't I see the raw workflow log for my scan?

Full tutorial

How to run a pentest scan in Cyberlop, and what happens next

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre