We had an issue with a large number of our jobs not running when the clocks changed.
The next runtime was set to a time/date in the past.

To get round this (not ideal), I ran all the jobs affected, and that seemed to work ok.

An issue we still have, is with jobs that monitor the age of files.
We have a number of them that monitor a pulse.log file, and if this file is older than:

30 minutes older than current time/date - {DATENOWADD(Minutes|-30|dd/MM/yyyy HH:mm)}

Then a service is restarted.

These jobs were running all the time, as this condition appears to be permanently met, unless you set the DATENOWADD to more than 70 minutes.

I have 20+ jobs that have this value set to 30 minutes, so have had to disable all of them, otherwise services are restarting all the time.

Does VisualCron run it's own clock, as the date/time in the variable appears to match the server clock?

We found one DST issue which we fixed in 6.2.1. About Date condition issue. Please test if you can reproduce it with 6.2.2.

---

Excellent, upgrading to 6.2.2 fixed the issue (was in the process of upgrading anyway!)

Many thanks as always Hendrik.

Thanks for the report and feedback!

---