When we have more than two or more services for the same Bull queue, we get this bug when the first one is closing. The setup might be that one is pushing and one is listening.
The solution is probably to keep track of how many queues we have listening, and only actually close the Bull/Redis connection when the last one closes.
When we have more than two or more services for the same Bull queue, we get this bug when the first one is closing. The setup might be that one is pushing and one is listening.
The solution is probably to keep track of how many queues we have listening, and only actually close the Bull/Redis connection when the last one closes.