Manuel Astudillo
Manuel Astudillo
@devashishg do you have a minimal example that reproduces the issue?
This is not currently possible but we have a new feature in the pipe called "sequential jobs" that would work kind-of, in the sense that jobs would never overlap but...
Well I am not sure about the release date, but this is most likely going to be a Pro feature, as it is quite involved to implement.
Thanks for the issue. Regarding the getters, for groups you must use the special groups getters, getGroups, getGroupJobs, etc: https://api.bullmq.pro/classes/v7.QueuePro.html#getGroups Regarding the issue with max concurrency, we need to check...
I tried with the following code and the concurrency was respected, I tried different variants and they worked. I will try another test case with manual retries. ```ts it('should respect...
I created a more involved case with manual retries and it seems like I can reproduce it.
We have a fix that should be released today.
There is actually a timeout which is by default 10 seconds: https://api.docs.bullmq.io/interfaces/v5.WorkerOptions.html#drainDelay
We could have an atomic script that deletes everything. Also the queue needs to be stopped so that no new data appears after its completion. I can add this as...