Skip to content
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

LastFireTime and NextExecutionTime of Trigger #173

Closed
dotnetstep opened this issue May 4, 2014 · 1 comment
Closed

LastFireTime and NextExecutionTime of Trigger #173

dotnetstep opened this issue May 4, 2014 · 1 comment

Comments

@dotnetstep
Copy link

I don't know this is issue or I am using it wrong way.

I am using JobStore : Sql Server and It works fine.

I have one job that some time take one minute to execute or sometime less depend on data. I have configured job to run every ten seconds. I have configured attribute for job so only one instance of job run.
Current Time : 04:30:00 AM
Now It display that Job Next execution time : 04:30:10 , but job started at 04:30:00 take 50 second to execute so next time it will fire on 04:30:50 but still it display 04:30:10 when it execute on 04:30:50. Same goes on.

Let me know if you need some more information.

@lahma
Copy link
Member

lahma commented May 5, 2014

This works as designed Quartz considers your trigger misfired as it didn't run when it was supposed to (job's concurrent execution protection prohibited it). You need to tweak your misfire handling configuration.

@lahma lahma closed this as completed May 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants