Scheduled Cron every morning at 4am misfired and now runs a lot #2138
Replies: 3 comments
-
I think it misfired because a server was restarted but now the job runs every time it finishes and not once a day like the cron is setup to do. |
Beta Was this translation helpful? Give feedback.
-
Update again. Next fire time is incorrect. When does a misfire just go back to its scheduled run time? |
Beta Was this translation helpful? Give feedback.
-
For some reason our next run time is scheduled for 8am instead of 4am like the cron is set to do? How is next fire time being set? If its on a cron? Doesn't seem to be working properly. |
Beta Was this translation helpful? Give feedback.
-
Hello,
We have a scheduled job running every morning and I think it misfired and now it just keeps running a lot.
This is how it was setup the misfire.
trigger.WithCronSchedule(cronJob.Cron, x => x .WithMisfireHandlingInstructionFireAndProceed());
How does it know when to stop running the misfire?
How can I get it to stop retrying?
This keeps popping up in our logs
{"@timestamp":"2023-09-14T11:04:33.0188810-04:00","level":"Information","messageTemplate":"Handling 1 trigger(s) that missed their scheduled fire-time.","message":"Handling 1 trigger(s) that missed their scheduled fire-time.","fields":{"SourceContext":"Quartz.Impl.AdoJobStore.JobStoreTX","MachineName":"---------","Environment":"Production"}}
Beta Was this translation helpful? Give feedback.
All reactions