5 days ago
I’m running n8n on Railway
I’m experiencing an issue where my webhook workflow does not stay responsive continuously. The workflow is:
Set to Published / Active
Using Production Webhook URL
EXECUTIONS_MODE=regularNo stuck executions visible
Sufficient RAM allocated
No visible OOM errors in logs
However, the webhook stops triggering the workflow automatically. The only way to make it work again is to manually click “Execute Workflow” or reconnect/redeploy components.
im using webhook to a elevenlabs
did anyone have a similar problem?
1 Replies
Status changed to Awaiting Railway Response Railway • 5 days ago
5 days ago
For most users on Railway running in EXECUTIONS_MODE=regular, the fix is adding a specific environment variable that prevents n8n from spinning up a new subprocess for every execution. In Railway's shared environments, these subprocesses can sometimes fail to report back or cause the main listener to hang.
Add this variable to your Railway service:
EXECUTIONS_PROCESS=main
By default, n8n uses own, which forks a new process for every single trigger. Switching to main keeps everything inside the primary process, which is significantly more stable for low-to-medium volume workflows on Railway.