All 11 n8n JSON snapshots matched. Both requests went to the wrong customers.

Description and use

In an n8n workflow, HTTP requests were sent to wrong customers due to lineage tracking bug. Audit detected mismatch; repair restored correct ancestry.

Problem

Outgoing HTTP requests in an n8n workflow addressed the wrong customers despite matching JSON snapshots.

Outcome

The audit tool detected mismatched ancestry indices, confirming wrong recipient requests. After applying the repair, the audit reported consistency and zero mismatches.

Workflow

• 1. Parent supplies four orders to child.
• 2. Child computes two branches (first two → A,B; latest two → D,C).
• 3. Each branch projects items, removing customer identity.
• 4. Merge selects one branch; parent recovers customer via $('Orders').item.
• 5. HTTP node sends requests based on recovered customer.
• 6. Audit tool compares returned items to expected parent input items.
• 7. Repair updates lineage traversal to use correct pairedItem metadata.

Evidence

Both outgoing HTTP requests addressed the wrong customers.

Source

The bug lives in the edge. n8n's pairedItem metadata links a result to its input ancestors.

Source

node experiments/lineage-boundary/audit-executions.cjs ... reports status: "mismatch", two findings and exit code 1.

Source