Data doesn't pass from "Execute workflow" to "When executed by another workflow" nodes

[M_Grant]

I am using the “Execute Workflow” node in a parent workflow to trigger a sub-workflow. The data is passed correctly, as verified in the Executions Mode, but it does not appear in the Editor Mode of the “When Executed by Another Workflow” node in the sub-workflow. The sub-workflow is configured with Input Data Mode: Accept All Data, and the parent workflow is set to pass structured JSON data.

Here are the details:

• Parent Workflow: The “Execute Workflow” node passes structured data, and I can see it in the input/output sections.
• Sub-Workflow: The “When Executed by Another Workflow” node does not display the input data in Editor Mode (shows empty fields or {}), but it works fine during actual execution (data is visible in Executions Mode).

What I’ve Tried:

1. Verified that the data is correctly passed from the parent workflow.
2. Checked configuration settings for both workflows.
3. Attempted to pin example data, but it doesn’t resolve the issue.
4. Replaced the “When Executed by Another Workflow” node, but the problem persists.

Screenshots:

• [Screenshot left]: Parent workflow’s “Execute Workflow” node showing correct input.
• [Screenshot right]: Sub-workflow’s “When Executed by Another Workflow” node showing empty output.

Question:
How can I make the input data visible in Editor Mode for better debugging and workflow building? Is this expected behavior or a bug?

Any guidance would be appreciated!

Last 2 nodes in parent workflow:

First node in sub-workflow:

Information on my n8n setup

• n8n version: 1.84.3
• Database (default: SQLite): Default
• n8n EXECUTIONS_PROCESS setting (default: own, main): Default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker Compose
• Operating system: Ubuntu 24.04

[hubschrauber]

The sub-workflow test-execution isn’t really connecting with the parent-workflow execution. They’ll be independent things when initiated from the editor.

When your parent workflow calls the sub-workflow, the execution of the sub-workflow you see then is associated / connected to the parent’s execution.

Assuming you are on the community edition, if you register it, one of the extra “free” features you get is a “Debug in Editor” button that appears on an execution. That copies the execution data into the editor for debugging. See docs. That might be the thing you are wishing for.