If you have your system date set incorrectly, the Scheduler will still make a timestamp based on that incorrect date.

Even if you then set your system clock to the right time, the scheduler will wait for the next update, based on the previous timestamp (even though that was incorrect from the wrongly configured system clock).

What's more troubling is that there is no way to reset the last timestamp for a schedule that has an incorrect "last run on" date. You just have to create a new schedule from scratch and make sure your system time is correct, before you do it.

regards,
halcyon

PS It is debatable whether this is a bug in technical terms. However, from a point of view of security it is, because the scheduler should not be so easily fooled and lead to a compromise in system security.

...PS It is debatable whether this is a bug in technical terms. However, from a point of view of security it is, because the scheduler should not be so easily fooled and lead to a compromise in system security.