I’m trying to setup N8N using queue as execution mode with around 10 workflows using cron triggers and each gets triggered around 5-10 seconds. After running a while, I saw a repeated series of logs like below:
Started with job ID: 7749994 (Execution ID: 15500895)
Started with job ID: 7750006 (Execution ID: 15500905)
Started with job ID: 7749995 (Execution ID: 15500897)
Started with job ID: 7749996 (Execution ID: 15500899)
Started with job ID: 7749997 (Execution ID: 15500900)
Started with job ID: 7749998 (Execution ID: 15500903)
Started with job ID: 7749999 (Execution ID: 15500901)
Started with job ID: 7750000 (Execution ID: 15500907)
Started with job ID: 7750001 (Execution ID: 15500906)
Started with job ID: 7750003 (Execution ID: 15500902)
Started with job ID: 7750004 (Execution ID: 15500908)
Started with job ID: 7750002 (Execution ID: 15500909)
Started with job ID: 7750005 (Execution ID: 15500904)
(node:7) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 global: completed listeners adde to [Queue]. Use emitter.setMaxListeners() to increase limit.
This is the logs on the N8N Main process. I’m using the old cron node instead of schedule node.
Is the warning emitted because there were more than 10 Queue events emitted?
If it is for Queue, I’m thinking to eliminate the warning as it was expected to have more than 10. Is there anyway to remove the warning?
I am very sorry to hear you’re having trouble. This has come up in a few other threads already, and you might want to follow these related threads instead of opening a new one:
