Can't get data from postgres nor subworkflow node

Questions
,
1

Describe the problem/error/question

i can’t get the data from the subworkflow nor from the postgres in the same execution

Please share your workflow

Main workflow:

Helper subworkflow (which I also tried to bundle in the main workflow first but got the same problem)

Share the output returned by the last node

image
image1366×735 44.9 KB

the subworkflow’s output is consistent with what I expected

image
image1158×541 41.3 KB

but the Execute Workflow node doesn’t output that, with or without the "do nothin"node

i’ve also tried the Postgres node to get the transcripts in the main workflow (you see it deactivated now) but it only brings the output from the database with only one link with transcript, even though the database already have the full transcripts

Information on your n8n setup

  • n8n version: 1.89.2
  • Database: Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): probably main, haven’t set this in .env
  • Running n8n via Docker
  • Operating system: Windows with WSL2
2

The TextManipulation node doesnt render. I can’t see what you are trying to reference.

You should be able to fix the psql node, if I can understand your goal more, with an improved query.

Or you could potentially use the n8n fetch execution node after the execute workflow node with the execution ID.

3

that node isn’t really important to the problem, because the issue is with the sub-workflow node. the point is that i wanted to bring the result of the subworkflow to the main one, which I thought was automatically fetched by the node without any workarounds.

4

Hi @koik

regarding the subworkflow, I just had the same issue. Turns out, this is a bug in recent versions of n8n. See the issue on GitHub here:

The reason seems to be if there is some form of asynchronous waiting in the sub-workflow. In this case, the result is not properly returned to the main workflow. Hopefully they can fix it soon… You can try downgrading to older versions before.

Regarding the problem with Postgres in the main workflow: I think it returns multiple items. You can put an aggregate node after it, so that all items are combined to one list. Maybe this helps

1 Like