New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any way to monitoring missfired job? #111
Comments
I understand that the problem is that when using a worker pool, sometimes jobs are waiting to be processed, and their next execution time will likely be expired next time. In this case, I would suggest extending the |
Java-quartz has |
@joint-song, a configuration property may be introduced in the upcoming release to address this requirement. |
@joint-song, PR #129 introduces a dedicated channel for managing misfired jobs. Providing a channel instead of a configuration flag gives the user more flexibility and control. Let me know if this aligns with your requirements. |
Yes, this solved my problem well, thanks for your help! |
I found some jobs because of short
OutdatedThreshold
or insufficientWorkerLimit
configuration were missfired. How can I find these situations as soon as possible?The text was updated successfully, but these errors were encountered: