Repository navigation
Problem: Job redo Option #314
Description
This is a follow up for #240
Jobs should have the option to configure how to handle a downtime of the scheduler.
transientjobs that do not need redo-ing even if their execution was skippedpermanentjobs 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.
Reacted by Joel C
Activity
jonathanhickford commentedon Aug 22, 2018
Any mileage in an option that gives the
permanent_consecutivescheduled jobs the information to determine itself what to do?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:
maennchen commentedon Aug 22, 2018
@jonathanhickford I'll consider that when implementing it. I'm already working on
v3where this should be included. Since I'm doing that in my free time it'll take some time though.