Home / Help centre / Integrations & API
Integrations & API
My CI job stopped waiting before the scan finished. Why?
The ready-made CI snippets poll every 30 seconds, up to 120 times, which is about one hour. A larger app can take longer than that. The job then stops waiting, but the scan keeps running in Cyberlop, so open Recent Scans to see the result.
Why this happens
The wait step is a loop. It asks GET /api/ci/result/{scanId} whether the scan is done, sleeps 30 seconds, and asks again, up to 120 times. That adds up to about one hour. The in-app documentation says a typical scan of a small app takes roughly an hour, so a bigger app can run past the loop.
Slow runs are common. Rate limits make a scan slower, never failed, so a busy period can stretch the time well past the usual hour for a small app.
How to fix it
- Open Recent Scans. The scan your job started is listed, and its Trigger tells you it came from CI.
- Click the row to open the scan detail page. A scan that is still running keeps going without the pipeline, because scans are durable and do not depend on the job.
- Wait for Completed. Then read the Findings tab.
- For the next run, raise the loop count in your own copy of the file. Raise it only as far as your CI tool allows.
- Look up the time limit your CI tool sets for one job. If that limit is lower than the loop, the tool ends the job first and the wait step never reaches its last poll.
Still not working?
If the scan shows Failed rather than still running, read what the failed banner means. If nothing started at all, see what to check when CI cannot trigger a scan.
You can also stop waiting on purpose. Start the scan in CI, end the job, and read the result later in the app. Many teams do that for large apps, together with a CI/CD step that only triggers. Questions? Write to us at the contact page with the scan's time and name.
Related questions
- How long does a scan take?
- How do I check a CI-triggered scan's result through the API?
- What does "Scan failed — The scan could not be completed" mean, and what should I do?
- Why is my scan taking much longer than usual?
- Why did my CI job pass even though Cyberlop found critical issues?
How to add security scanning to your CI/CD pipeline
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Wiring it into your pipeline?
Share what you are building and we will help you set up the right token, profile and job.