10 days ago
Then it's a transient infrastructure issue on Railway's end. The diagnosis confirms the build is fine and the same code deployed successfully yesterday.
Contact Railway support with deployment ID a0d1fcb6-0cfe-4590-b3d8-a8d7b8cd22da. They can investigate the container creation failure.
1 Replies
Status changed to Awaiting Railway Response Railway • 10 days ago
Status changed to Solved brody • 9 days ago
9 days ago
Chat told me again to Contact Railway support with this deployment ID: 11f09f72-8f14-4922-b67c-0b43d124efb9
Mention:
Consistent failures since May 1 at the CREATE_CONTAINER stage
Build succeeds every time
Same code deployed fine on April 30
Multiple redeploys have all failed at the same stage
Status changed to Awaiting Railway Response Railway • 9 days ago
Status changed to Solved brody • 9 days ago