You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: