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

Adding a repeatable job with an end data in the past should raise an exception #2568

Closed
manast opened this issue May 16, 2024 · 2 comments
Closed
Labels
enhancement New feature or request

Comments

@manast
Copy link
Contributor

manast commented May 16, 2024

As it is easy to mistakenly add a job that has an old endDate argument that will result in a repeatable job that never repeats, it would be useful to throw an exception to make it aware for the developer that this is the case.

@manast manast added the enhancement New feature or request label May 16, 2024
@fabianboerner
Copy link

Yes, we had a problem because we calculated the repeatable end date. The service parameter where changed and the enddate was calculated in the past.
The result was the return value from queue.add was empty and we could not identify the error first.

@roggervalf
Copy link
Collaborator

#2574 it's covered by this pr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants