When testing one of my workflows, I’ve had an issue where an HTTP Request node appears to be stuck as it runs for much longer than it should. Upon refreshing my page and attempting to re-run the flow, any API calls that I make will instantly fail citing an invalid protocol error. So far, the only solution has been restarting my N8N instance. Is this a known bug or am I just mishandling instances where the HTTP Request node gets stuck? Any advice is appreciated!
Hi @JWeitzel Sorry you’re running into this!
Can you share an example of when this is happening? Is this happening with one specific workflow, or many? Are these workflows hitting different endpoints / requests, or are they from the same provider?
Also, could you let us know the following:
- n8n version:
- Database (default: SQLite):
- n8n EXECUTIONS_PROCESS setting (default: own, main):
- Running n8n via (Docker, npm, n8n cloud, desktop app):
- Operating system:
Additionally, if you have any n8n logs / server logs, those would be helpful! You can read more about n8n logging here: Logging | n8n Docs - Setting your log level to
debug would give us the most information