Description: My workflow setup is as follows: A main workflow triggers a sub-workflow that encapsulates fixed operations. The sub-workflow’s output should be returned to the main workflow’s execution node for downstream tasks. Expected Behavior: The sub-workflow final node’s output is correctly…

No reply for long time, I have to continue investigating myself. Actually here are two workflow synchronization issues: First Issue: When a sub-workflow contains a wait node, the parent workflow execution node receives input from the wait node instead of final results. The normal execution flow: …

I have the exact same issue, the subworkflow with a wait and responese outlook node returns the input, not the output from the outlook node containing the human response. Running n8n on servers. I am guessing that your fix only works for local n8n, since you are modifying source code from my underst…

I ran into this same problem today. The output of a sub-workflow which has a wait node that is resumed by a webhook call returns the wait node’s input data, not the sub-workflow’s output data. This seems like a pretty serious bug. I hope it can be fixed soon.

Yep, having the same issue since around v0.95 or so. Switched to using webhooks but they time out too fast for what I’m doing (waiting response from a user). So as of right now, there is no workaround available from what I can see unless I just make the next node a child of the sub-workflow. Not ide…

I lost a good amount of time to find out that this was the problem… It seems that the wait node needs to wait a certain amount of time, e.g. with 3 seconds it worked, but with 3 minutes it didn’t work anymore…

Same issue here! Main workflow: [image] Sub Workflow: [image] As you can see the Wait node from Sub-Workflow is returning a different JSON from the one received in the Main-Workflow.

Same issue, serious problem. This blocks my approach to modularize a complex flow and handle each step of my automation in a subflow, with the parent flow just orchestrating the subs. I do not believe this is an exotic approach (instead, the rational way to handle complexity) and expect this bug to …

[image] N8N Community node: Introducing Workflow PubSub for effortless workflow decoupling Built with n8n This package provides custom nodes for n8n that allow seamless event-driven communication between workflows within the n8n ecosystem, creating a flexi…

Hello, I get this message when trying to install : *Error loading package “n8n-nodes-workflow-pubsub” :Expected double-quoted property name in JSON at position 603 (line 22 column 3) * I hope that the devs will find a way to resolve this “Sub-workflow with wait Node” thing. I really would need to …

Sub-workflow with wait Node Returns Incorrect Output to Main Workflow

Questions

Parintele_Damaskin October 16, 2025, 7:51pm 11

Maybe this helps in your case…

Topic		Replies	Views
Problem with subworkflow run not returning the output to the parent Questions	6	351	December 29, 2025
Problems obtaining the response from the sub-workflow Questions	13	578	September 25, 2025
Parent workflow is continuing while a subworkflow is waiting for webhook Known Issues wait , execute-workflow	7	924	September 9, 2025
Should a Parent Execute workflow wait if a call to a Sub workflow uses a Resume on WebHook or Wait node? Questions	12	1369	June 20, 2023
This discussion is about a bug in n8n where sub-workflows containing a "wait" node (webhook, Telegram, etc.) fail to return their output to the parent workflow Questions	7	115	April 5, 2026

Sub-workflow with wait Node Returns Incorrect Output to Main Workflow

Related topics