queue.push() doesn't check if task id is currently a worker

Just a clarification on my part. I was noticing that long running tasks aren’t considered for duplicating checking on ‘id’ when pushed into a queue. For example, I could have a queue of concurrency 10, and push in a task that’ll take 10 minutes to execute. It’s id property is long_running_task. Once work begins on it, I can push another tasks, `` into the queue and it’ll begin working, despite having the same id as the long running task in the worker. I would have thought that if there’s a task with the same ID that’s working, any new tasks with the same ID would be rejected/merged?

[NathanHazout]

An old task, is it still relevant? When doing concurrent processing, I expect the queue would prevent tasks with the same ID to be processed at the same time, as it could lead to conflicts…

[iulianivg]

This problem still persists today.

I have a database watcher which looks if new collection is added. If so, add the collection to the queue. Then I have a long running task applied to each collection which can take 6-8 minutes to complete and accesses shared resources (files on the server, modifies them, emails them, etc.)

The queue works amazing on the first task, but then when it has 3-4 other pending tasks it takes 2 at the same time despite {concurrent: 1, batchSize: 1, afterProcessDelay: 1000, maxRetries:10, retryDelay: 1000 }

Edit: even if you check if ID is the same, the queue still ends up executing 2-3 tasks at the same time. I’ll get back with an update when I get results