I have a problem with the “Execute Workflow” node. In the newer version, this has the option “Wait For Sub-Workflow Completion”. My expectations of this option: The sub-workflow is executed if the calling workflow does not wait for the response but continues to run, similar to a webhook with a respond node where subsequent nodes are also executed after the response to the caller. The problem is that the Execute Workflow with the “Wait For Sub-Workflow: false” option set starts the workflow, but the Sub-Workflow is immediately aborted. Is that how it should be?
After many tests, I finally found the error:
If you use the settings for On Error = “Continue (using error output)” in the “Execute Workflow” node (also in v1.1), the sub-workflow is started and ended immediately. “Stop workflow” and ‘Continue’ do not lead to this problem.
I thought of something.
Can you Show a screenshot of the main and sub workflow when it has the issue?
Then I can verify my thought of what the issue is.
Outside of this topic:
I have found another error. When renaming a node, if you Tab to Cancel and then press Enter, the change is not canceled but applied.
Looks like it is working fine here.
I did notice you have the latest execute workflow inserted though. So maybe that is the issue.
Can you try with my flow (including the old execute workflow node)
However, the workaround via HTTP/Webhook still works well. I would also say better, as I can explicitly pass attributes to the workflow here, which unfortunately is still not possible with the “Execute Workflow”. You are forced to put a set node or similar in front of it.
However, I would then have to block subflows that are only to be used internally on the proxy from the outside. But IP whitelist is now also available in n8n.
