Trigger missed

[andriussi]

Hi
I just encountered orchestrator skipping one scheduled robot. After looking at the console I noticed, that it did a restart at 10:01:02 and the robot was supposed to run at 10:01:00. However in this case i guess the 10:01:00 happened while the orchestrator was restarting.

I think it would be useful to have a check that there are no robots scheduled in the next 5 mins or so before doing the restart.

Console:

Schedule:

Executions:

[Ghitafjorback]

Did you manage to find a solution for this issue? We have SEVERAL of these happen. :(