HTTP request node identified a internal error as Success

[kayong]

HI guys, i am pretty new to n8n. please be patient and guide me on what i missed. thank you!

i have 3 questions on my workflow.

my http request faced an internal error, but the success route is chosen instead of error route. is this a bug or expected behavior ?

this is the internal error that i am getting

i re-run the exact same HTTP request again , on a individual node of its own, and there is no issue with it.
is this a internal error at n8n server ? or the target server?

lastly , how can i fix the above issue from happening again ?

Please share your workflow

Information on your n8n setup

• n8n version: 1.51.1
• Database (default: SQLite): default
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): self-host docker
• Operating system: the defualt one that documentation suggested

[ria]

Hi @kayong

Thanks for posting here and welcome to the community!

You may want to update to the latest n8n version 1.62. to see if the issue persists. It should also give you a better error description.

[kayong]

hi ria, thank you for the prompt response.
i have done a server update and “retried with original saved workflow” and still getting the same error . is there anything i can do ?

or should i wait for new occurrence of such situation?
(i am unable to manually recreate the situation / error)

[ria]

Hi @kayong

Thanks for the feedback.
We have raised an internal ticket for this to look into it.

Please keep sharing any other observations you may come across.

Thanks!

Will keep you posted here