a month ago
I asked the Railway chatbot: ok, so what do we do?
It's reply:
Contact Railway support. This is a persistent builder infrastructure issue affecting your service. Provide them with these three failed deployment IDs:
aaa1898d-0932-4b53-a7ad-da6341870ae1eded8f13-8990-4e74-b1dd-9c0b6c74dda0234c4dd7-b0e8-472e-8a3c-e1767df84fe1
Tell them:
- Builder starts, generates correct build plan, but never executes
npm cior build commands - Timeouts after ~20 minutes with no execution logs
- Same code deployed successfully earlier today
- Pattern repeats across multiple fresh deployments
They can investigate the builder infrastructure on their end and potentially route your service to a healthy builder instance.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We're aware of an issue affecting builds where deployments get stuck without producing build logs. This is being actively investigated by our platform team.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 27 days ago