bottleneck icon indicating copy to clipboard operation
bottleneck copied to clipboard

Retry behaviour

Open fkoemep opened this issue 1 year ago • 0 comments

As it's stated in the README you should return a ms value from the "failed" job and the retry will start automatically after that elapsed time, the problem is that the job executes immediately and will bypass almost every limiter setting thus getting rate limited when the retry jobs start.

Would it be possible to change the default behaviour and send it to the back of the queue instead of starting with a "EXECUTING" state?

fkoemep avatar Feb 21 '24 14:02 fkoemep