My scheduled scan ran at the wrong hour. Why?

Why this happens

A start time has no meaning without a timezone. The app reads every schedule in the one timezone set for the organisation, and that setting starts at UTC, so if nobody changed it a 09:00 start means 09:00 UTC, not 09:00 where your team sits.

Daylight saving can add to the confusion. Named zones keep their local start time through clock changes, but the matching UTC time shifts by an hour.

How to fix it

1. Open Settings → Organization and read Timezone for schedules.
2. Choose the zone where your team works. A named city zone follows local clock changes.
3. Click Save changes.
4. Open Scheduled Scans and check the start time of the schedule that ran early or late. Make a new schedule if the start itself was wrong.
5. When you compare, read the run time and the timezone in the same zone. Mixing UTC and local readings is the most common source of a one-hour gap.

Still not working?

• The capture does not show what happens to existing schedules when the zone changes, so check the next run after you save.
• Confirm the scan came from the schedule. The Trigger field on its Overview tab helps.
• Remember that large apps take longer, so a late finish is not a late start. Compare the Started time, not the finish.

Learn more in how daylight saving affects schedules and how to change the schedule timezone. Still wrong? contact us with the schedule and the time you expected.

Related questions

• How do I change the timezone scheduled scans use?
• Do scheduled scans shift when daylight saving time changes?
• How do I choose the time a scheduled scan runs?
• How is a recurring schedule's timing worked out?
• Why didn't my scheduled scan run?

Full tutorial

How to schedule security scans in Cyberlop

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre