Data Not Flowing into Sub-FLow

[yerb]

Describe the problem/error/question

I am trying to pass data from the parent workflow into the sub workflow so I can utilize parallelization and dynamic variables.

I have watched countless videos, scraped through this forum, and there has not be a single solution to why this is happening leading me to believe it is a bug.

If it is user error, please help me correct it and understand why it didn’t work despite me following all the settings I needed to.

What is the error message (if any)?

There is no error message. The sub workflow executes with the hardcoded data I entered into it, but when evaluating the “When Executed by Another Workflow” trigger inside the sub flow, there is no output. As if no data from the parent workflow, despite it triggering the sub workflow and completing the actions, is passing into the sub workflow.

Please share your workflow

Main (Parent) Flow:

SubFlow:

Share the output returned by the last node

The Execute Workflow1 node in the parent flow outputs on its last iteration “ip 10.0.0.5”. The loop node showcases both items in the Done Branch. There is no output from the “When Executed by Another Workflow” node in the sub flow.

Information on your n8n setup

• **n8n version: 1.101.1
• **Database (default: SQLite): SQLite
• **n8n EXECUTIONS_PROCESS setting (default: own, main): own
• **Running n8n via (Docker, npm, n8n cloud, desktop app): cloud
• **Operating system: macOS

[Qkhanhss1]

@yerb

om the parent workflow, despite it triggering

Do you connect right subflow ? In my case , i do exactly your flow and in run successfully

[yerb]

Yes, I am sure it is connected to the right sub flow. The image below shows the node from the parent workflow and its output while also showing which sub flow is is connected to “Try Again SubFlow”:

This next images shows the sub flow and the node that is supposed to be retrieving the output data seen in the previous image:

Both nodes were executed, yet no data is passing to the sub flow node.

Still not sure how you got it to work. Does me being on a trial version effect anything (I would not expect it to)?

[yerb]

Have you taken a look at my other reply to you showing that nothing is passing through?

[moosa]

try this:

I did was change mode to ‘run once with all items’

[yerb]

It is not working. Changing the mode setting to “Run once with all items” does not work. Plus that shouldn’t be an issue because the original mode allows me to utilize parallelization. The image below shows that executing the parent function and getting successful alerts still does not activate the sub-flow in on the right:

This image shows the same sub-flow and its name with its flow ID which matches the ID in the parent flow:

and yet I still get nothing:

Even manually executing the sub-flow doesn’t link the data from the parent flow - I still get null:

It is very strange that it is working for you and the other poster on this thread - which leads me to believe either it is a trial related problem or something else related to my account.

How do I call for a mod or support to access this situation? This hinders a lot of utilization for me right now.

[moosa]

why do not you give this one a try:

I am also using free trial

and when i manually triggered no data was passed but data was only present when i opened sub workflow from

give it a try and let me know.

[yerb]

I think you are right.

You can only see the data being passed through if you go to executions, or click “View sub-execution”. However if you are in the sub-flow editor and click on the nodes, it only shows you the fields with “null” or pre-set values; not the actual data being passed from parent flow.

I am not sure if this is by design because its a sub flow.

I can mark this as solved since there is a way to see the data coming through. I

If you are trying to use the sub-flow in a way that incorporates the data passed from parent flow then you would just have to use blank fields when setting up the nodes, run the parent flow, and then go evaluate how your data passed by looking at “Executions,” not “Editor”.

Thanks moosa.

[moosa]

my pleasure.

you should mark my reply as solution