16 days ago
After updating my n8n instance to the latest version on Railway, all my workflows stopped executing correctly.
Symptoms:
Every workflow I previously created is now stuck in “queue” / “queued” state.
The executions never actually start.
Triggers that used to run automatically (cron/schedule, webhook chains, etc.) no longer fire.
Manual restart or re-deploy does not fix it.
Timeline / what I did:
I updated n8n to the latest version.
After the update, I noticed new workflow runs were not processing. The UI shows them as queued.
I tried updating and restarting n8n multiple times from Railway.
After those restarts, the problem is now global: every single workflow that used to run is no longer running at all.
Impact:
This breaks all of my automations. These workflows were already in production.
Before the update, everything worked normally.
Request:
Can you please help me investigate why executions are stuck in queue on Railway?
Is there any known issue with background workers / queue mode / concurrency in the latest n8n build on Railway?
Do I need an extra worker process or special config after the update (for example separate main process vs worker process)? Because this was not required before.
Environment notes:
Hosted on Railway.
n8n was upgraded to the latest version right before the issue started.
The issue happens for all workflows, including ones that previously ran fine with the exact same logic.
This is urgent for me because these workflows are part of my live business operation
Please advise how to recover the normal execution
Thanks,
Chawan C.
1 Replies
16 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
16 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 16 days ago