cann0nball
Results
2
comments of
cann0nball
I can confirm this behavior. It seems it's trying to update the previous job repeat, that already finished, leaving the next scheduled one untouched. It seems to work correctly, if...
I've tried with the latest version (5.53.1) and it doesn't fix the issue we have. Also tried to reproduce with a test, but couldn't. Surprisingly, with a short offset, like...