Honestly, I am not sure what happens with the job if the time clock jumps one hour forward. None of my jobs are actually configured to start between 02.00 and 03.00
but when you have jobs starting at specific intervals, this indeed might happen...
I read your feature request, but I am thinking more generally for this one. If a job is skipped (for example, because the server was down for maintenance, DST move, any other reason why it was skipped or not started...) B&R should detect this and start the job anyway even if the schedule is missed... I might need to take this to the discussion table