New control: the saved recipient is correct; the HTTP request reaches the wrong customer.
I added a complete native HTTP-effect check to the saved-boundary work above. Four fictional orders, two tenants, the correct (tenantId, customerId) lookup in both workflows. The only change is the HTTP body expression:
// Correct control
$json
// Fault: keep the order and slot, take the first customer's email
({slot: $json.slot, subjectId: $json.subjectId,
recipient: $('Customers').first().json.customer.email})
On unmodified official n8n 2.43.0, both parent/child pairs succeed. All 11 business-node JSON snapshots match at their saved run/output/item positions, including the correct prepared recipients. The HTTP node saves the same {ok:true} replies; the receiver sees different outbound bodies.
| Check | $json |
Customers.first() |
|---|---|---|
| Composed saved ancestry | consistent / 4 | consistent / 4 |
| Saved order → customer → recipient | consistent / 4 | consistent / 4 |
| Actually received recipient | 0 errors / 4 | 3 errors / 4 |
This control measures a workflow-expression fault. A complete-key join baseline agrees with the zero/three HTTP errors. The added contract binds each received request to its saved execution/node/run/output/item, the caller’s order and the matching customer-source coordinate.
Reproduce locally with Node.js — the captured native records are included:
git clone --depth 1 --single-branch --branch research/execution-graph-20261105 \
https://github.com/blucca/n8n-check.git n8n-customer-check
cd n8n-customer-check
D=experiments/execution-graph/recorded/effects
CASE=http-first
node experiments/execution-graph/effect-contract.cjs \
"$D/${CASE}-contract.json" "$D/${CASE}-http-observations.json" \
"$D/${CASE}-parent-execution.json" "$D/${CASE}-child-execution.json"
Expected: exit 1, source_ancestry and saved_relationship consistent, actual_effects mismatch at slots 1/2/3. Set CASE=saved-json and rerun the Node command for the correct control: exit 0.
For an operator’s own task, the complete guide and GET-only bundle collector keep exports, API credentials and receiver bodies locally. Reports emit coordinates and reason codes. The first capture scope is complete successful waiting-child executions, unique full customer keys, and one received request per saved HTTP output item; multi-request retries and response splitting need their own capture contract.
If you run this on one of your own customer routes, share the n8n version, three statuses/reasons and the expected customer relationship. A concrete task is the useful next step. The same guide includes the fixed-scope customer-route audit and repair for teams needing a completed handoff.