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.

Sign up for GitHub

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

Jump to bottom

Handle a triggering error when using randomOffset for jobs #47

Open
ivan-brko opened this issue Nov 16, 2020 · 0 comments
Open

Handle a triggering error when using randomOffset for jobs #47

ivan-brko opened this issue Nov 16, 2020 · 0 comments
Labels
bug Something isn't working
Milestone
v0.3

Comments

@ivan-brko
Copy link
Owner

Sometimes, when using random offset for jobs the following error happens:
Exception in thread "DefaultDispatcher-worker-3" org.quartz.ObjectAlreadyExistsException: Unable to store Job : <jop_name>, because one already exists with this identification.

After that this task will not be triggered anymore.
@ivan-brko ivan-brko added the bug Something isn't working label Nov 16, 2020
@ivan-brko ivan-brko added this to the v0.3 milestone Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
v0.3
Development

No branches or pull requests
1 participant
@ivan-brko