Manuel Astudillo

Btw, here you can find some example code from the tests that is running correctly: https://github.com/taskforcesh/bullmq/blob/master/python/tests/worker_tests.py

Your code is too long and complex. Why don't you start from a working code such as the one in the test case and built from there? for sure you...

Ok, let me know when you can produce a test based on the working tests from BullMQ and we can take a deeper look into it.

@pburdette, the behavior you are describing is very unusual. Most likely, there is an issue in your worker's process callback. Could you share more information or code so that we...

I think this works as designed. Since you are adding the same repeatable job, only the first time it will be immediate, then it will just repeat according to the...

I created a test to specifically cover this case. It works perfectly, the problem is that you are probably getting already the second iteration of the job before you remove...

I talked to @roggervalf about this privately, but for the record, the bug is produced by BullMQ when creating a queue with the empty string as its name. After that,...

Most likely you are trying to remove an active job. As long as a job is active and locked by a worker it cannot be manually removed.

This error can only occur when you manually remove a job with [```remove```](https://api.docs.bullmq.io/classes/v4.Queue.html#remove). So somewhere in your codebase you are removing jobs manually.

Are you sure about this? reason for asking is that in Unix, if the parent process is killed, its children are killed automatically, so it is strange that you still...