Issue with http node output containing 'error'

Describe the problem/error/question

I’m facing trouble with dealing with the ‘error’ output generated by a HTTP node, whether it’s via the Include Response Headers and Status == true approach, or with the On Error == Continue (using error output).

The issue is, the data in the ‘error’ object is not being correctly parsed/considered by the nodes following the HTTP node (Set node/IF node). [See screenshots below]

Concerned wf:

The Set node:

Information on your n8n setup

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

Hey @shrey-42,

Can you share a small workflow that reproduces this issue?

Hey @Jon , sure :

Update: modified the workflow to include both the cases

Something strange with this scenario is, that after executing the workflow (and not destroying the data), if i re-run the Set nodes, the correct value populates in the node output:

Hey @shrey-42,

Thanks for the example I will get a bug ticket created shortly for this.

Quick Edit: Internal ticket for this is NODE-1048

1 Like

New version [email protected] got released which includes the GitHub PR 8394.

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