N8N sequential executions and Kubernetes

[fcecagno]

This feature request is documented already:

Option for blocking parallel workflow execution

When using cron trigger with a short interval it can happen that a workflow is running in parallel. When the workflow is chewing through some data the second instance would do the same and this builds up. For the time being I use a blocker like the one below. But I think this is something that can be handled in an option for the workflow even better. { "nodes": [ { "parameters": {}, "name": "Start", "type": "n8n-nodes-base.start", "typeVersion": 1, "posi…