Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Running scans

Running scans

Can a long analysis get cut off part-way?

Quick answer

A long analysis is not cut off mid-thought. Agents run with a very high turn limit and periodic heartbeats, and rate limits or temporary API errors are retried with growing pauses. A scan can slow down for hours, but the workflow resumes where it stopped.

The short version

No, a long analysis does not get cut short. Cyberlop sets the turn limit for its agents very high on purpose, because a deep read of a large codebase can take a great many steps and a limit should never be the reason a scan stops.

How it works in Cyberlop

Three parts of the design keep long work alive.

  • High turn limit. Agents can take a very large number of steps before any limit applies.
  • Heartbeats. Agents send regular signals, so the workflow can tell a busy agent from a stuck one.
  • Durable retries. Rate limits and temporary API errors trigger retries with exponential backoff at the workflow layer.

Every scan runs as a durable, crash-recoverable workflow. If the AI provider limits your requests, the scan waits. According to the in-app Documentation, it can wait out even a multi-hour rate window before it carries on. From your side, the scan gets slower. It does not turn into a failure.

This does not mean a scan can never fail. It can still end as Failed for other reasons, and the scan page then shows a red banner at the top of the page. Read what the failed banner means if you see one.

What to do next

  • Leave a slow scan alone unless you need the result soon. Waiting out a rate limit is normal.
  • Look at the Overview tab to see whether cost and token counters are still moving.
  • If the pace worries you, read why a scan can run slower than usual.
  • Use your own AI provider key if rate limits keep slowing you down. See API key or OAuth token.
Full tutorial

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

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Still stuck?

Tell us what you see on screen and an engineer will help you sort it out.