Set node error next to HTTP node - ERROR: Cannot read properties of undefined (reading 'name')

Questions
,
1

Describe the problem/error/question

If timeout is set the HTTP node output contains some error which cannot be processen in the next Set node in some cases.

What is the error message (if any)?

ERROR: Cannot read properties of undefined (reading ‘name’)

image
image1272×714 83.3 KB

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.236.0
  • Database (default: SQLite): PostgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 22.04.2 LTS

Summary

  1. In my opinion the request abortion by timeout should be treated as “fail” and handled by Retry on fail in node settings.
  2. I can assume that the output of a node execution in case of timeout contains some extra/invalid data that produce error in the Set node because if you just pin the JSON result you won’t get error. You have to execute the process to face the error.
2

Hi @Nick_K_H :wave: Welcome to the community :tada:

Thanks for all the information you included in your post. I’d say this might not be intentional, and I can replicate this on both the version you posted about (0.236.0) and on latest (1.1.1).

I’ve gone ahead and flagged this for our developers to take a look into, and I’ll post once I have any updates!

1 Like
4

@Nick_K_H I believe this has been fixed and released in 1.2.2.

2 Likes