-
Notifications
You must be signed in to change notification settings - Fork 16.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Wait For Sub-Workflow Completion" = false causes execution to not run #13830
Comments
Hey @Fank, We have created an internal ticket to look into this which we will be tracking as "GHC-1147" |
Hey @Fank, I am not able to reproduce this, Below is an example workflow can you give it a run and see if it gives you the same issue?
|
I tried to build a reproduction as well, it is not easily reproduceable, but its there. |
Hey @Fank, Even running that workflow I just can't reproduce it, I can see the error in the log where something is undefined but I am not sure what it is. Do you happen to have the example trigger data that causes it and does it always fail? |
Bug Description
The main workflow:
When following setting is set:
Causes the execution on the subworkflow to not run:
This also caused following error on the worker node:
When I change it to:
Then the executions runs perfectly fine:
Debug info
core
storage
pruning
client
Generated at: 2025-03-11T13:29:21.206Z
To Reproduce
Expected behavior
That the execution runs like as it would wait.
Operating System
docker (self-hosted)
n8n Version
1.82.1
Node.js Version
20.18.3
Database
PostgreSQL
Execution mode
queue
The text was updated successfully, but these errors were encountered: