Next start time for absolute_repeat not correctly calculated - First repetition is skipped

A runtime definition like this
<run_time let_run="no">
<period absolute_repeat="01:00" begin="10:00:00" end="23:00"/>
</run_time>

results in a faulty start time after first execution. The first order starts at the begin of the period at 10:00 a.m., but the new calculated start time is not 11:00 a.m. as expected, but 12:00 a.m.

Subsequent start times calculated correctly and end of period is respected, too.

Clarification: JobScheduduler starts the order at the begin of the period (okay), skips the first repetition (error), and continues with the following repetitions (okay).