I am wondering how this catch up schedules at restart works.   Let's say that I have a program that starts at sunrise and this program has several steps after a set number of minutes and ends at sunsrise plus 1 hour. If I manually restart, for whatever reason,  the ISY (or IoP) at sunrise plus 30 minutes, will the 'catch up'   restart the program from the beginning, at the state it is supposed to be at that time, or not restart at all ?

I am asking this because I have noticed that after restarting  the IoP I have lights going on that I was not expecting to go on, and I am suspecting that the system is catching up.

21 hours ago, asbril said:

I am wondering how this catch up schedules at restart works.   Let's say that I have a program that starts at sunrise and this program has several steps after a set number of minutes and ends at sunsrise plus 1 hour. If I manually restart, for whatever reason,  the ISY (or IoP) at sunrise plus 30 minutes, will the 'catch up'   restart the program from the beginning, at the state it is supposed to be at that time, or not restart at all ?

I am asking this because I have noticed that after restarting  the IoP I have lights going on that I was not expecting to go on, and I am suspecting that the system is catching up.

I believe catch up at restart is only referring to the start time of the program.  Once the program is running it will run for an hour and finish an hour after it started, not "catch up" the steps by ignoring the 'waits'.

So in your example: "Let's say that I have a program that starts at sunrise"-- if it's after sunrise the program will start -- "and this program has several steps after a set number of minutes and ends at sunsrise plus 1 hour." -- the "wait" statements in your program have no way of knowing anything about catching up... they will still wait... the program will still take 1 hour to run.