You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: