Hi Railway team,

My n8n instance (service ID: primary-production-4e894) was working perfectly for 8 months until today when it auto-updated to n8n version 1.121.3.

Problem:

• All workflow executions now hang indefinitely (spinning, never completing)
• Even simple blank workflows with just a Manual Trigger fail to execute
• No errors in logs - workflows just never start processing

What I've tried:

1. Added environment variable N8N_VERSION=1.60.1 to rollback to stable version
2. Redeployed service multiple times
3. Added N8N_RESET_DATABASE=true to clear execution history
4. Checked deployment logs - no version rollback occurred despite variable being set

Current state:

• N8N_VERSION=1.60.1 is set in environment variables
• Service still deploys with n8n 1.121.3 (variable is being ignored)
• Railway template appears to hardcode Docker image tag to :latest

Request: How can I force my n8n service to use a specific Docker image version (n8nio/n8n:1.60.1) instead of :latest? The environment variable approach isn't working with your n8n template.

Alternative: Is there a way to edit the service's Docker image configuration directly, or do I need to delete and recreate the service?

Thanks for your help.

Where to send it:

1. Railway Dashboard → Help icon (bottom left) → "Contact Support"
2. OR: https://railway.app/help
3. OR: Railway Discord: https://discord.gg/railway

THEY'LL LIKELY TELL YOU:

"Delete the service and redeploy with the version pinned from the start."

Which is what I've been suggesting for the last hour.

WHILE YOU WAIT FOR THEIR RESPONSE

Just rebuild it yourself. Seriously.

1. Export workflow (you have it)
2. Delete Primary service
3. Create new one
4. Set N8N_VERSION=1.60.1 BEFORE first deploy
5. Import workflow
6. Done in 15 minutes

Railway support will take 2-24 hours to respond, and they'll probably say the same thing.

Your call: Wait for Railway support, or just fix it yourself in 15 minutes?