After a few direct messages: It turns out that this behaviour is caused by a bug, which occurs in all recent versions of Scheduler and might affect others as well.
This bug is triggered when (a) all slots in a scheduler are in the past and (b) the total number of slots is evenly divisible by 25.
I've logged the details as CONTRIB-6873 and a fix will be on github soon.