Home / Help centre / Running scans
Running scans
What does the trigger badge, such as Manual, mean on a scan?
Open any scan page and the trigger badge tells you how the run was started. Manual means a person pressed Scan. Scheduled runs show their schedule, and runs started from your pipeline use a different trigger. It sits beside the status badge in the page header.
The short version
One question drives this badge: what started this scan? A person pressing Scan in the app gives you Manual, either on a profile row or from the target page. Simple.
How it works in Cyberlop
You will find it in three places on a scan page.
- The header subtitle reads, for example, Profile: full audit · Manual run · Scan, followed by an eight-character scan ID that you can quote to support.
- A badge sits next to the status badge, so you might see Completed then Manual.
- On the Overview tab, the Trigger row in the Run details card repeats it. Short and clear.
A scheduled run shows the schedule instead of Manual, and runs started from a pipeline are the third kind of trigger. Activity feed entries for Start · Scan carry the same detail as a Trigger chip, so you can check it there too.
The badge says how a run began. It does not say who pressed the button, and for that you should look at the Run by column in Recent Scans, where each row shows an email address. Two different questions, two different places.
What to do next
- Open the scan and read the Run details card for the trigger, location, profile and times.
- Set up a recurring run in Scheduled Scans if you want fewer manual runs and a steady record of how the app changes.
- Find who started a run in the Run by column.
- For the whole page, read the scan detail tutorial.
Related questions
- How do I see who started a scan?
- How do I see when a scan started and finished?
- How do I open the profile a scan used?
- How do I see which commit a white-box scan tested?
- Where do I see how much a scan cost and how many tokens it used?
The scan detail page: how to read a Cyberlop scan from Overview to Diff
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.