Customer D’s order reached Customer A.

Both recorded runs succeeded. Follow a returned item to see where the parent’s recorded input and the child’s native origin part ways.

Loading the self-authored, recorded n8n case…

Follow the returned item

Choose a return. Inspect both ends of its thread.

Connecting the recorded executions…

Reading executions

The desk compares ancestry at the sub-execution boundary.

Choose a returned item to inspect its recorded and resolved origins.

Keep the structural evidence.

Download the finding, coordinates, and provenance. Business JSON stays out of the report.

Bring your executions to the desk.

Use two complete n8n API execution JSON records, saved with includeData=true. Choose the parent first to find the child execution it actually called.

Drop one or two execution files hereOr choose the files below.

The execution containing the sub-workflow call.

The complete execution identified by that call.

Choose a parent execution to begin.