Infinite list of canceled/error executions, dozens per second

[pldxaz]

Describe the problem/error/question

This thing has been hapenning a lot of times since I deployed two n8n instances. Sometimes a workflow that’s triggered with external thing such as Notion, RSS get bugged and generates an immense amount of error/canceled executions, and nothing is treated again. This is an extremely impacting issue because the error workflow is not triggered so I sometimes see the error after a lot of time.
Only workaround is to duplicate the workflow…

What is the error message (if any)?

Infinite ‘error’ or ‘canceled’ executions, a lot per second. Not possible to check since when it happens since the history is flooded.

Please refer to Endless list of canceled executions constantly appearing in execution list where I gave a lot more information.

Information on your n8n setup

Hi, I have been having this issue for multiple months (at least october, and I update n8n every 2 weeks or so. I self host n8n using Docker on debian 12 up to date, in queue mode with Redis, with postgres (version 16 and 17).
Still happens today with 1.86.0

[Kent1]

Did you try this

Bug - Dozens of errors per sec per workflow containing a webhook

I had the same error and solved it by removing some executions from the database. More specifically, executions with status “error” and no “startedAt” value. You can try this SQL query in your n8n database: SELECT * FROM execution_entity WHERE "startedAt" IS NULL AND status = 'error' These executions seems to be replayed by workers and cause these errors with activated workflow.

[pldxaz]

@Bug - Dozens of errors per sec per workflow containing a webhook

I had the same error and solved it by removing some executions from the database. More specifically, executions with status “error” and no “startedAt” value. You can try this SQL query in your n8n database: SELECT * FROM execution_entity WHERE “startedAt” IS NULL AND status = ‘error’ These executions seems to be replayed by workers and cause these errors with activated workflow.

Thank you for your answer. I will try this when the issue happens again. I hope this issue will be fixed once and for all at some point

[Kent1]

For me the problem was comming from network interruption (cause by a bad config with my haproxy to many request).
Maybe you a also network issue and sometimes communication between n8n, redis and your database have trouble, that’s why you have this errors sometimes