a month ago
I'm having a recurring issue with my project "rare-art" (Hobby plan), specifically with the Postgres service connected to my n8n instance.
Issue:
Intermittently, the n8n service stops responding and shows this error:
{"code":503,"message":"Database is not ready!"}
Checking the n8n Deploy Logs, I see repeated messages like:
"Timed out after 30000ms waiting for database connection recovery"
"Failed to hard-delete executions"
This suggests the Postgres service loses connection and doesn't recover on its own. The only fix that has worked so far is manually restarting/redeploying the Postgres service.
Frequency:
This has happened at least 3-4 times over the past two weeks (around June 30, July 2, and July 11, 2026), without me making significant configuration changes at those times.
Additional context:
- Reported usage in the "Usage" panel is low (under $1 USD accumulated this month), so it doesn't seem to be a resource limit issue.
- The project only runs a simple n8n workflow, scheduled to run once a day.
- Using the template: ghcr.io/railwayapp-templates/postgres-ssl:latest
- Region: US West
Could you help me investigate the root cause of these Postgres disconnections? I'd like to understand if it's a configuration issue on my end, a template issue, or related to Railway's infrastructure in that region.
Thanks in advance,
Caminos Tours
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
Adjust your n8n environment variables to make less resource-intensive pruning.
Tell me if you want executions data commands for that.
Also check the resource (memory) usage graphs in your Railway dashboard
Adjusting health-check timeout configuration or ensuring the connection string optimization