Sub-workflow final node

Questions
, ,
1

Hi community, I’m seeing odd behavior with a Sub-workflow. The execute workflow node (wait for completion turned on) outputs the same input it received {offset, id} instead of the sub-workflow last node output. The sub workflow ends in a single terminal “Set” node that outputs one item {count_email, offset} and all branches merged into it. In the sub-execution I can see the final node emitting the expected payload. However, the output of the Execute workflow node in de parent workflow does not get this output.

Any idea why the parent flow would get its own input back instead of the sub flow’s final output? Screenshot 1 = parent node showing identical input/output, Screenshot 2 = sub workflow final node output, Screenshot 3 = Sub-workflow overview.
Thanks in advance!

image
image1877×832 100 KB

image
image1880×782 96.3 KB

image
image1248×668 69.2 KB

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Hi @Sam_Bastiaens ,

did you had a view in JSON format of the output?
Because there is shown 1 item, 1 sub-execution.
I think you will see the sub-execution data in JSON format like a second item.

3

Thank you for your reply. I still don’t see it?

image
image563×323 9.35 KB

4

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