-
Notifications
You must be signed in to change notification settings - Fork 89
Open
Description
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?
Metadata
Metadata
Assignees
Labels
No labels