Manuel Astudillo

I would recommend upgrading to 5.7.7 even, as it will mitigate a potential issue we have discovered with IORedis in the case of network partitions.

> I am interested in the Pro version of BullMQ, but I don't see any documentation on how to balance parallel jobs across workers. For example, if there are 3...

Here we have a test that demonstrates ```changeDelay``` works as expected: https://github.com/taskforcesh/bullmq/blob/67c3b8b7af266ba8be82fa1e095ac86c8b86e6a1/tests/test_job.ts#L815 If you have a succinct variation of the given test that shows it is not working as expected,...

I think it is possible this has to do with the max events length, as you are processing very quickly, the Redis stream holding the events may get trimmed before...

what does ```myQueue.getDelayed()``` return after removing the repeatable job?

Yes, this works as "expected". As there is only one complete set, we just apply the removeOnComplete set for every job. So in this case the best would be to...

I think it is better to keep the number of queues low, as it is easier to maintain. However, I wonder why you need different settings for the queues, could...

Sometimes it is useful to store information in a separate system, for instance you could store some data in a different Redis host or another database system with the result...

> Not having a filtering options makes it really hard for cases where there is a centralized consumer and multiple producers Filtering in ```getJobs``` would only be useful for debugging...

> That's not feasible, it would introduce coupling with tens of consumers, and the producer service would have to be modified every time a new result queue is needed. Thanks...