My colleague created a nice recursion in n8n that brought down our server. I managed to see the workflow processes in the process window.
My question is, is there a way to find out which workflow created the recursion (was called 5000 times)? Would be nice to point my colleague directly to the problematic workflow.
My feature request: Can we limit workflow execution per minute to prevent this? Or create a limit that deactivates the workflow if reached within X minutes.