Subworkflow data are not passed on

[Drearily5829]

Describe the problem/error/question

Hello good people,

I have a Telegram bot that is assigning calendar events to payments in an accounting app. Everything worked well but since the 1.51.2 the data from the calendar subworkflow are not passed back to the “mother” workflow even thought the workflow succesfully finishes and generates data. I did some changes recently to that workflow so I am not 100% sure that it is because of the update.

I realized that the sub workflow hands over the data fine when there is no event in calendar. I generate an (one) empty item basically for that case.

When there is three items, the sub workflow finishes, the Execute another workflow is green, but does not have any data and the workflow stops.

I was definitely able to get more than one item from the calendar subworkflow before. Was there some change that would change how my workflow works? Or can you see the reason why it does not return more then 1 item?

What is the error message (if any)?

I am not getting any errors

Please share your workflow

There are some data pinned, sufficiently annonymized.

Share the output returned by the last node

Information on your n8n setup

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

[barn4k]

What are the Execute Workflow’s node settings in the main WF?

I see only one issue with the sub workflow where the Merge node may act unpredictably

Plus the CallendarData node has a reference to the Date Collector node, which may not be triggered if the data goes throw the first switch path.

[Drearily5829]

Thank you for your input.

@barn4k

What are the Execute Workflow’s node settings in the main WF?

Everything default

@barn4k

I see only one issue with the sub workflow where the Merge node may act unpredictably

I wanted to output the input date as well as it came in handy (and it is easier than extracting it from the calendar event data) recently in one case. I am using this calendar workflow in multiple workflows. I might try dropping this feature and see if it works.

I would be able to drop the merge if I would extract the events date from its data. That might be worth trying as well. Just thinking out loud…

@barn4k

Plus the CallendarData node has a reference to the Date Collector node, which may not be triggered if the data goes throw the first switch path.

I am aware of that. The calID path is used only when extracting a specific event and I do not need to output the input date in this case.

[Drearily5829]

Took some of the feedback and voila - it works.

It still did not work when I deleted the date from the CalendarData node so it was not that. Not entirely sure why it did not work but the new workflow has less nodes so I am happy.