Hi, thanks for the reply!
Unfortunately the issue you linked is not related to our issue, Daylight Saving Time was an indicator of the underlying issue it seems. I am able to reproduce the issue today by updating a recurring job manually.
Planned crontime (Should fire each day at UTC 01:00):
(0 1 * * * )
Updated to (Should fire each day at UTC 02:00):
(0 2 * * *)
Did the job update around 15:00 UTC and it causes an immediate execution of the job. The expected result would be a planned execution on the next occurrence 02:00 UTC.
I have a feeling the issue arises because the LastExecution lies outside of the new time:
(0 1 * * *) --> is from 10-Nov 01:00 to 11-Nov 01:00, last execution is 10-Nov 01:01
(0 2 * * *) --> is from 10-Nov 02:00 to 11-Nov 02:00, last execution is 10-Nov 01:01 (Notice LastExecution time being outside range of cronschedule).
Is this considered as the preferred behavior or would this be an issue?
It makes sense that a job gets executed immediately when its outside the scheduled time, but in my opinion this behavior should not trigger when a job gets updated by the AddOrUpdate method.