Manuel Astudillo

This is a bit more difficult to do with the current design than what I would like. I will keep it in the backlog as a nice to have feature.

This is a nice proposal, we have already started a discussion about a very similar functionality here: https://github.com/OptimalBits/bull/issues/340

I think it may be better to decouple the data from the ```add``` method to the ```process``` method. What I mean is that instead of creating the dependency explicitly per...

I see. I will try to think about some solution that covers that use-case. The problem with the approach that you took is that if all the calls to add...

It is implemented in BullMQ: https://docs.bullmq.io/guide/flows Not sure if it will be backported to Bull though.

You will need to either save the jobIds in some external database, or if the amount of delayed jobs is not huge use a graphical front end such as https://taskforce.sh...

@amitav13 no, not possible atm.

@amitav13 it will work most of the time but it is not robust, many edge cases can happen here, for example, the delayed job maybe is already running, or your...

@axos88 it does not remove it immediately, please check the documentation: https://github.com/OptimalBits/bull/blob/develop/REFERENCE.md#queueadd

yes, however Date is also a sword with two edges, if you retain based on date you may end filling up all redis memory.