Entire Workflow Freezes when adding a HTTP Node

[Jesse_Danku]

The workflow starts out well, all native functions such as webhooks, if/else conditions, etc. work well and can execute them.
But as soon as I add HTTP node, not only does the HTTP node break, but the entire workflow also.
It freezes and continues to doomspin (never ending “waiting for execution” error when I click on the first node in the workflow → Listen for test event)

1. I tried deleting and recreating the workflow

2. N8N is up to date

3. The HTTP requests are correct as they are working fine in a separate workflow with the EXACT SAME details in the http.

4. no errors in the deployment logs

I filmed this 2-minute Komodo video just now explaining and showing the exact issue:
https://kommodo.ai/recordings/ICfn885RSPDkiSg8EmHA

[Jesse_Danku]

Here are a few screenshots:

[Wouter_Nigrini]

Hi @Jesse_Danku, please note that when you want to test the execution from your 3rd party tool, make sure you add the correct test url with “-test”, otherwise the workflow waiting to be executed will never be fired. You will see there are two urls provided on the webhook node, one for testing and one for production. Make sure you use the correct one.

Your workflow is not hanging, it’s just waiting to be called which will never happen if your 3rd party tool does not use “-test”

[Jesse_Danku]

My third party tool does use -test. Please watch the video I attached there, I literally show the problem. It’s firing just fine withot the HTTP Node. Here is a screenshot from the video. If the solution was that easy I would’ve solved it already.

[ramin1]

i had a similar problem once. i have workflow with webhook trigger and a faulty node. when i fixed the node issue, my workflow executed as normal. so i think your http node has a problem so change it to a get request to https://www.google.com and check your execusion

[Jesse_Danku]

Tried it with dummy data, and the same thing happens, unfortunately. It just freaks out. Maybe it’s a railway server thingy.

[ramin1]

Strange!

so if you only add webhook and call it then pin its data and then add the dummy http node and execute your workflow, your workflow execute normally?

[enzpic]

Hello,

Such a nice video !
did you try to trigger the webhook with a curl request ?
do you get any answer ? (with and without HTTP node)

Any hints in the web browser console ?
Maybe you can run the same test, console with and without HTTP node.

Also, is it acting the same if you try http node with a dummy manual trigger ?
I guess yes, as this HTTP node work in other workflow.

[Jesse_Danku]

unfortunately no. I show it in the video. as soon as i add a http node the workflow no longer works.

[Jesse_Danku]

hi. i get an answer only withot the http. everything breaks after i add a http.
there are no hints, tried it in different computers too just in case.
It is acting the same with a dummy manual trigger.

[enzpic]

Could you copy the workflow please ?
I would like to reproduce on my environment.

So far, I tried similar workflow (thanks to the video), and it works without issue.
Only concern, I see that HTTP node is making a POST to https://jsonplaceholder.typicode.com/posts/1 (if i copy correctly)

On my side, it returns a 404 error, and I can not activate the flow.
Can you try with a GET maybe ?

[alen8n]

Hi! I’m experiencing the exact same issue, the entire workflow freezes, I can’t execute neither the HTTP or other nodes in the workflow.
I’ll see the node loading undefinitely, then if I check executions, it shows that execution failed in a few (18-40) ms with the following errors:

I’m running self-hosted n8n from a docker image (n8nio/n8n) on runway
I noticed this error in the 1.121.3 version first, then updated to 1.122.1 but didn’t solve anything.

Another weird thing which is also visibile from @Jesse_Danku screenshot is that the HTTP node is not outlined in red as one would expect for a node that caused an error. It’s like the execution doesn’t even start as long as the HTTP node is there (although if I try calling the webhook trigger, it says the workflow has started, even though it actually doesn’t).

If I remove the HTTP node, everything works again.