Execute Sub-workflow issue

Hello

Describe the problem/error/question

I have a master workflow which call a sub workflow at its end.

The Sub workflow receive data but not all the parameters

The “to_send_to_xx” does not receive anything.
I tried to change its type but it is same issue.
We can see in the sub workflow that this parameter is defined to Boolean but the Output displays it as Sting.

Any clue ?

What is the error message (if any)?

No error

Please share your workflow

Master workflow ends with

Sub workflow starts with

Share the output returned by the last node

[
{
“filename”: “xx.pdf”,
“file_binary”: {
“mimeType”: “application/pdf”,
“fileType”: “pdf”,
“fileExtension”: “pdf”,
“data”: “JVBERi0…UVPRgo=”,
“fileName”: “xx.pdf”,
“fileSize”: “30.3 kB”
},
“dest_folder”: “https://xx.sharepoint.com/sites/xx/Shared%20Documents/General/xx”,
“to_send_to_odoo”: null,
“warning_msg”: null
}
]

Information on your n8n setup

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

This appears to be a bug because the default value of that parameter is “on” but the output value is actually null.

The workaround is to simply toggle it off and back on again. When on the boolean value is set to true correctly.

:warning: if you think this solved your problem, please mark this as the solution! :smiling_cat_with_heart_eyes:

Thank you @Gede_Suparsa

It seems your screenshot if about the Master workflow and not the sub workflow.
Do the sub workflow receive data correctly ?

On my side, apparently, data are correctly sent but not correctly received.
Unfortunately, toggle the variable did change anything :frowning:

Best regards

Yes it does. I’ve re-run it and the value does get passed correctly from the parent to the child workflow.

Here’s the parent workflow execution.

and here’s the sub-workflow that’s associated with it.

And I’ve found the relevant bug associated with the initital state.

2 Likes

Thank you for the link : Boolean field in sub-workflow input shows as enabled but is actually null · Issue #20149 · n8n-io/n8n · GitHub

I will follow it until the bug is solved

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.