//Pułapki n8n · krytyczna
Execute Workflow + Wait nodes cause data loss
When using Execute Workflow node with Wait nodes in the sub-workflow, data can be lost on resume. The sub-workflow execution may not properly return data to the parent workflow after the wait period. Avoid using Wait nodes in sub-workflows called via Execute Workflow — use webhook-based patterns instead.
- Kategoria
- n8n_general
Źródło: lista pułapek n8n-mcp, którą utrzymuje autor narzędzia · Treść w oryginale, po angielsku, w formie, w jakiej trafia do agenta.
Błędy, które agenci AI popełniają w n8n
- SplitInBatches + Wait nodes cause state loss
- Never use append on sheets with formula columns
- $env expressions blocked in Code nodes
- saveExecutionProgress fills disk space
- IF node uses branch true/false not sourceIndex
- Code node $input.all() vs $input.first()
- Per-item execution on large datasets
- Webhook node response must be sent explicitly
- Error Trigger workflow must be separate
- $getWorkflowStaticData global loses data in loops