Issue with Sub-workflow execution using Execute Sub-workflow node (v1.2)

Questions
1

Hi dear community, :heart_hands:

I’ve designed a workflow that uses the Execute Sub-workflow node (version 1.2) to send input data and trigger another workflow (sub-workflow).
The node appears to be configured correctly, and its execution is reported as successful
(1 item, 1 sub-execution).

1
1648×214 26.9 KB

However, it seems that the sub-workflow either doesn’t run at all, or the input data isn’t passed correctly — the final output is null.

2
2531×215 16.4 KB

I’d appreciate it if anyone has had a similar experience or could offer some guidance. :heart:

2

Did you defined the workflow input in tool by adding in the subworkflow trigger the task == {{ $json.item.value}}.

After you add in subworkflow trigger the input you expect, go back in main workflow and check the tool (you will see an input).

1 Like
3

Hi dear friend, :heart_hands:

Thanks for your response.
As you can see in the first screenshot, the workflow and input are correctly selected from the executed trigger.

image
image903×686 33.8 KB

In the second screenshot, you can also see that the configuration is correct — but the output still shows . null

image
image602×428 17.6 KB

What’s strange is that in the Executions tab, everything looks fine: the trigger node runs properly and receives the expected value, as shown in the screenshot.

image
image892×358 21.8 KB

4

Is there any node after ‘Start S1’ ? Or it goes directly to the subworkflow(does tour subworkflow has a Wait node?

5

Hi,
The Start S1 node sends a request to start the workflow, and in the target workflow there’s a receiver node right after that — followed by an Edit node.

image
image504×284 8.79 KB

6

You didn’t mentioned how did you executed the workflows(pinned data, test etc…)

But I think that is OK, in production since

P.S I am better at speaking with machines :slight_smile: