The task is scheduled correctly and runs at the correct time for approximately 3 days. Afterwards it is no longer executed and in the dashboard we get phenomena like this:
In English, it is telling us that the next execution is 37 minutes ago which does not really make sense at all.
By omitting the part setting the time zone to the local time zone (that is, using the default time zone configuration UTC) with all other configuration remaining unchanged the task is scheduled and executed correctly for any length of time. Therefore we strongly assume a problem related to the timezone setting when calling the RecurringJobManager.
Version
1.8.11 and 1.8.14
Storage package
Hangfire.InMemory 0.10.3
Configuration logic
Custom job filters
None
Problem
By scheduling a task using the following call:
The task is scheduled correctly and runs at the correct time for approximately 3 days. Afterwards it is no longer executed and in the dashboard we get phenomena like this:
In English, it is telling us that the next execution is 37 minutes ago which does not really make sense at all.
By omitting the part setting the time zone to the local time zone (that is, using the default time zone configuration UTC) with all other configuration remaining unchanged the task is scheduled and executed correctly for any length of time. Therefore we strongly assume a problem related to the timezone setting when calling the
RecurringJobManager
.