Replies: 1 comment
-
I did further analysis on this and found out that my quartz service was restarted after the last successful run and before the next fire utc time. In my opinion this could be an issue that it stopped running any further jobs. My service is running only on one POD. @lahma please correct me if I’m wrong. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a job which is scheduled to be running every 8 hours. it was working fine. but suddenly it stopped working. When I investigated it, I observed that it was showing a different time than the next fire time.
var trigger = (await scheduler.GetTriggersOfJob(jobKey));
if (trigger.Count != 1) return;
var nextFireUtc = trigger[0].GetNextFireTimeUtc()?.UtcDateTime;
//I have only one item in triggerI have also seen this description But didn't understand it much. Could you please guide me on the reason behind it?
Note that the time returned can possibly be in the past, if the time that was computed for the trigger to next fire has already arrived, but the scheduler has not yet been able to fire the trigger (which would likely be due to lack of resources e.g. threads).
Quartz version: 3.5.0
.Net: 6
Beta Was this translation helpful? Give feedback.
All reactions