Thank you @guibescos for pointing that out! -1 has been turned to 0.
Exactly that’s why we have a lot of smart people here.
with -1 the code was doing exactly what you wanted, 4 seconds future intervals instead of 60 seconds lol 
(predictive bugs)
the case study is unaffected by this bug, since it is using slightly different version of the code