Jobs with attempts > 0 have different priority?

[DavideViolante]

Description

I noticed the following in our app:

1. there are X+Y jobs in waiting queue: X jobs have priority 50 and attemps 0, Y jobs have priority 25 and attemps > 0
2. the jobs with priority 50 go into the active queue BEFORE the jobs with priority 25

I was expecting that jobs with priority 25 go before the other ones with priority 50, even if the ones with priority 25 have attempted once or more.
Which is the correct behaviour?

Bull version

v3.14.0

[manast]

It probably has not do with the number of attempts, but rather with the retry. I found an issue in the retry script that is moving jobs back to the wait queue but ignoring the priority.

[DavideViolante]

Is there a date when this is going to be addressed?
Is there a previous version that is not affected? I remeber this was not happening in the past if I remember correctly, but absolutely not sure.
If I'm wrong, is there a way to force programmatically the waiting jobs priority 25 attempts>0 to go into active queue before others?
Thanks

[manast]

I cannot give a date. But PRs are welcome of course.
I do not think this is a regression because the code for it is missing, likewise the unit tests.

[DavideViolante]

Ok thanks.
Do you think using the delay field applied to the X jobs (priority 50) can be a good workaround to prioritize the Y jobs (priority 25)?

[manast]

maybe works for your use case, there may be edge cases where it does not work as you expect.

[DavideViolante]

I tried it and it seems it doesn't work with delay either.
Waiting for a fix.

[manast]

🎉 This issue has been resolved in version 4.12.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀