DO NOT use this library if you need sequential order execution your jobs.

[misterjt]

I spent two week of development with kue, and just yesterday i noticed weird sorting.
Just think twice before using this library, if you need sequential order execution your jobs.
Developers probably forgot about kue and will never fix it.
#691
#693

[punmechanic]

Developers probably forgot about kue and will never fix it.

I know certainly that TJ holoway (one of the lead devs) stopped using node a while ago and only wants to continue to maintain koa

[pursual]

Any suggestions on a sequential task library?

[misterjt]

https://github.com/OptimalBits/bull

[hockeytim11]

#708
Just wanted to reference a fix I worked on.

[behrad]

I spent two week of development with kue, and just yesterday i noticed weird sorting.

If you've read the docs and searched issues carefully you would find out that Kue is a priority Queue not a sequential task library (however you can use it as a sequential task library) and that there exists an issue with specific task ids (10, 100, 1000, ...) in job orderings...
That means you are infected if you are creating many jobs concurrently or your queue contains many jobs. e.g. you will be hit by job id 10 for the first time, (if 9 and 10 are queued up, 10 will be run sooner)

Developers probably forgot about kue and will never fix it

I'm trying to improve Kue for about 2 years now. Since this is a one-man work for now, my busy hours delays kue 1.0 release, however any members, helpers, ... are welcome.

DO NOT use this library if you need sequential order execution your jobs

I can't figure out why are you trying to achieve with this kind of statement. You are free to use everything you want/need/prefer. However this is not normal to open up an issue with such a title.

[behrad]

Just wanted to reference a fix I worked on.

I'll try to check you PR thank you @hockeytim11