## Describe the problem/error/question
My issue is with the HTTP request node.
When I execute the node manually, it works, but when I test the complete workflow, or make it active and test it in production, the HTTP node does not work. It receives input, but does not provide output. Then again, if I execute it manually, it works.
I have tried enabling “Always output data”, “Execute Once”, “Retry on Fall”. Aso I have tried disconnecitng the upper flow, still the same result, stuck in the HTTP node.
## What is the error message (if any)?
Unkknow error message appears after a while in my second code node, but I think it’s because it reaches a timeout, as there is no data coming from the second data flow (the one with the HTTP request)
## Please share your workflow
## Share the output returned by the last node
## Information on your n8n setup
- n8n version: – 1.91.3
- Database (default: SQLite): – default
- n8n EXECUTIONS_PROCESS setting (default: own, main): – default
- Running n8n via (Docker, npm, n8n cloud, desktop app): – n8n cloud
- Operating system: – Win 11
Welcome @Carlos_Salas
Change to POST and test again
2 Likes
Hi @interss,
I have tried your proposal, but still the same issue happens, the workflow stops at the HTTP request node.
In any case, the action the HTTP request has to do is to get because it’s searching ClickUp for tasks that contain a specific email. So when I run POST it returns an error:
I see.
I looked at your workflow and found this line break in the HTTP node URL
Although when I open the HTTP node, the line break does not appear in the expression
It may be just my imagination, but I think it may be causing an invalid URL when running in a production environment.
I made this small correction to your workflow, so you could open a test workflow, add your credentials and necessary information and test this workflow below to see if the problem has been resolved
Here is a suggested workflow
1 Like
Hi Rubens,
Obrigado for testing that out! 
I tried the workflow you shared, but unfortunately, the issue is still there.
What’s puzzling is that the HTTP request node doesn’t return any error—it simply doesn’t work. Even stranger, it works fine when you trigger it manually.
Maybe I need to set up a secondary agent that “manually” activates the HTTP request. 
Thanks again for your help!
Hello @Carlos_Salas
It’s interesting to talk about this, because I thought about using a NODE FIELDS before HTTPS to process the data. I thought that this possibility could work.
Feel free to continue the conversation, if you wish
I am having the same problem here. This time with a Pipedrive API HTTP Request
Working when executing step, not working in execution.
In testing:
In execution:
