Is there a way to adjust the backoff count?

[ahathaway]

Looking for a way to set the backoff algorithm to something much lower, like say 3 runs before failure. Jobber seems to run up to about 10 times and this is a bit excessive for my use case.

[dshearer]

Not right now but it can be added.

On Mar 7, 2019, at 8:27 AM, Alex Hathaway [email protected] wrote:

Looking for a way to set the backoff algorithm to something much lower, like say 3 runs before failure. Jobber seems to run up to about 10 times and this is a bit excessive for my use case.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[ahathaway]

That would be great. I have some db operations that I'm running and continuing to run them so many times when they fail is having some other adverse effects on the system as a whole. I have three environments that I use Jobber in for this project and so having different throttle settings per job in the YAML would be a great add I think so that I can fine tune things a bit more on this end.

[henres]

Hello,

Is it possible to configure this and the treshold in second ? Like, restart 3 times with treshold of 30 seconds. We have to many alerts when it's failed. So 10 x ~30 alerts every 5 minutes. I'ts a bit too much :D

Thanks

[henres]

Hello,

Another thing is that you can't have the same system as cron. When a cron failed, it do nothing and wait for the next schedule. If we can set the backoff count to 0, we can have similar result than cron.

Thanks for your works