RoboTask forum

Last sundaynight, 30th March at 2:00 AM (02:00) the daylight saving time in Europe started. This means the time skips to 3:00 AM.
We have a task which runs every hour at xx:57:00.

In the logs, I've discovered that suddenly the task was started at 3:00, I assume because officially the task at 02:57:00 was skipped ofcourse. That time never existed. Robotask was shocked about this , and executed it. Am I right? Is this by design? Is this a setting?

n the logs, I've discovered that suddenly the task was started at 3:00, I assume because officially the task at 02:57:00 was skipped ofcourse. That time never existed. Robotask was shocked about this , and executed it. Am I right?

Yes, you are right
Scheduler trigger uses local time of computer. Thus, this effect occurs during the transition to summer/winter time.
Also, this effect occurs when you wake up the computer and the control time has passed while the computer was asleep.

Allright, good to know. Thanks!

Is RoboTask designed to immediately trigger missed scheduled tasks like the 02:57 run when the system clock jumps forward due to DST, or was this execution at 03:00 a fallback mechanism?