Manuel Astudillo

Besides the callstack it would be useful to see the actual code snippet where the exception is thrown, as it seems like it is coming from user code.

So is the code above working or are you getting the error still? and do you have the complete error stack of the error?

Unfortunatelly there is not a lot information here for us to take any action...

This is a bit tricky actually. You would need to make sure that none of the workers is still locking the job before you can delete it. Force a deletion...

A lock on a job uses a unique token that is generated for every Worker, so that only the worker that actually tool the lock is able to unlock it....

The concurrency setting can only be set on each worker, so if you have two workers then it will add the concurrency factor of every worker, in the example above...

If the lock is still there, then the worker is still running for that job. Another thing is that that worker may be stuck doing nothing due to some wrong...

@faisal-merchlink It is possible to achieve what you are asking with BullMQ Pro. You need to use the groups feature and set the maximum concurrency to 1, that will effectively...

This PR should address this issue: https://github.com/taskforcesh/bullmq/pull/2465

The locks will expire themselves automatically after max 30 seconds (default value).