Replies: 1 comment 3 replies
-
Retried jobs and rate limited jobs become delayed jobs so they are kind of competing against each other on arriving at the head of the queue, I think that is the problem you are experiencing. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a way to make sure the retries are processed before the existing queue?
My use case is using a rate limited queue to smooth out traffic flow to rate limited api's. However, if a particular job fails and should be retried, it ends up at the end of the queue. I would like to prioritize the failures fifo to the original time they were added to the queue.
Update:
I found this related question, #1963 (reply in thread)
However, this is not what I'm observing.
Is there something I'm doing wrong for these expectations?
I created a simple test.
Beta Was this translation helpful? Give feedback.
All reactions