-
-
Notifications
You must be signed in to change notification settings - Fork 148
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
Problem: Job redo Option #314
Comments
Any mileage in an option that gives the For example say I have a job scheduled every hour which has the purpose of sending reminder notifcations. If I missed a number of runs I might want to only send reminders for events that have not yet happened. I think for that usecase I'd want to be able to pass the job arguments for both:
|
@jonathanhickford I'll consider that when implementing it. I'm already working on |
This is a follow up for #240
Jobs should have the option to configure how to handle a downtime of the scheduler.
transient
jobs that do not need redo-ing even if their execution was skippedpermanent
jobs that would like to get executed once after the period of scheduler being down (no matter how many cycles they have missed). Like backup jobs.permanent_consecutive
- (a better name is more than appreciated) that need to be redone exact the number of times they were not executed. I can imagine like jobs incrementing some counters. I believe I would be able to come up with a real-world scenario, but I need some thinking to come up with it.The text was updated successfully, but these errors were encountered: