The workflow execution reaches the HTTP Request node and starts successfully. However, after a couple of seconds, I receive an “Execution stopped” message with no output, making it appear as if the module didn’t start at all.
Despite this message, the HTTP Request node continues running in the background (since my HTTP request takes a long time to complete - up to 15 minutes). Eventually, the HTTP Request node does complete and produces output, but the workflow doesn’t continue to the next steps. Instead, the entire workflow gets stuck in a “running” state indefinitely.
Information on your n8n setup
- n8nVersion: 1.103.2(route back to 1.101.3, same issue)
- platform: docker (self-hosted)
- nodeJsVersion: 22.17.0
- database: postgres
- n8n EXECUTIONS_PROCESS setting: default
- Running n8n via Docker
- executionMode: regular
- concurrency: 1
- license: enterprise (production)