Workflows And Nodes

A Code node returns `return {json: {foo: 'bar'}}` instead of an array. Downstream Set node receives only one item even when upstream sent 50.

Per docs, every node must emit `items` as an array of {json, binary} entries; the Code node should return `return items` or `return [{json: ...}, ...]`. When a single object is returned, treat it as a one-item array — but operator should fix the node to preserve fan-out semantics.

Operator writes `={{ $json.id }}` in a node that runs after a Merge node, expecting it to reference the original HTTP node's response.

`$json` always refers to the current input item, which after a Merge node is the merged item. To reach back to a specific upstream node, use `={{ $node['HTTP Request'].json.id }}` or `={{ $('HTTP Request').item.json.id }}`. Document the scope explicitly so the workflow survives refactors.

A workflow imported from a 0.x export runs branches in a different order than the new `executionOrder: v1` default. Downstream Merge picks up data from the 'wrong' branch first.

Set `settings.executionOrder: 'v1'` on new workflows (n8n default) — branches run in declared connection order. Imported legacy workflows may use `'legacy'`; pin the imported setting explicitly so semantics are deterministic across upgrades.