The idea is:
To add a feature in the Enterprise Cloud dashboard that automatically detects and optionally disables individual nodes stuck in repeated execution loops (a.k.a. “doom loops”) — rather than waiting for full workflow or instance instability. Ideally, the system would flag problematic nodes and allow users to deactivate them directly from the UI.
My use case:
On a recent deadline-critical weekend, a single looping node caused my entire instance to go down repeatedly. I had to spin up a self-hosted version to meet the deadline. Looking at the logs and Postgres backend, it was clear which nodes were the problem — and a single SQL update would have resolved it. With this data already accessible, it seems feasible to offer this as a user-facing Enterprise feature.
I think it would be beneficial to add this because:
This would reduce downtime, prevent full workflow deactivation, and lower support burden. For enterprise users working under tight deadlines, having visibility and control over problematic nodes — before the entire instance is affected — could be the difference between shipping or missing a milestone.
Any resources to support this?
I can share:
- Recent support threads with n8n Cloud team, confirming current process and limitations
- Internal logs and DB inspection showing the ease of identifying bad nodes
Are you willing to work on this?
Happy to advise, test, or help define the detection logic based on real-world examples.