Execute Sub-workflow doesnt respond

Describe the problem/error/question

  • the problem is that the subworkflow is not responding to the main workflow after completion. There have been no errors in the subwork flow and ive added a set node to guarantee an output yet the main workflow still does not recieve it

What is the error message (if any)?

There was an error: “The workflow did not return a response”
this is the error im getting from the main workflow

Please share your workflow

Share the output returned by the last node

[
{
"Success ": “0j75ksc711144d6mpkpqcot7f4”
}
]

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:

Hi,

take a look at my post here. Had a similar situation and figured it out just today. Maybe it is the same issue, but therefore you may need to post your workflow here.

i just read the thread and saw you found the problem at the merge node. i do have a merge node right before the workflow ends to collect data from GSheets node, the only i can thik of is to remove the merge entirely and duplicate the last couple nodes for each GSheets node. do you have any other advice?

@daelan_alviz I am by far no expert in n8n, but looking at your workflow, I assume you have kinda the same issue.

What do I mean with that? As far as I understood, the workflow ends at the first node not connected to something else and the data are sent back here to the main workflow. I assume that the “Edit Fields 1” node is the issue. The workflow ends here, as it is not connected to some other node.

I don’t know what the route to the “Edit Fields 1” node is supposed to do, but if it is an alternative route to the “switch” node route, you should split the route after the “workflow execution” node, by use of an if or switch node. If you need that information to be sent back together with the other data, you need to connect it to the appropriate node later in the workflow by use of an aggregate node.

Hope that makes sense and of course, hope my assumptions are correct :wink:

1 Like

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