2 months ago
Staging service courtvibe-staging (service ID: 90c8fa2b-009e-4c2a-a38d-f7d4a87fa61b ) — 6 consecutive failed deployments in sfo region. Build succeeds every time but container scheduler times out at exactly 22 minutes with ‘Failed to create deployment’. Your own diagnosis tool confirmed it as an infrastructure error. Last successful deploy was Jun 8 at 11:11 PM HKT. Would not let me asked privately so posting in forum
10 Replies
2 months ago
We're aware of these transient build queue issues and are actively working on improvements. Please cancel any queued builds and wait for the issue to resolve on our side, since additional redeploys can compound the queue.
Status changed to Awaiting User Response Railway • 2 months ago
Railway
We're aware of these transient build queue issues and are actively working on improvements. Please cancel any queued builds and wait for the issue to resolve on our side, since additional redeploys can compound the queue.
2 months ago
How long will it take to resolve been going on for over 8 hours
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
We don't have an ETA for resolution, but your previous deployment is still running and serving traffic normally while new deploys are affected. Please cancel any queued builds and hold off on redeploying, as additional attempts can compound the issue.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
nothing queued just 6 failed deploys. Will these deploy automatically when the issue is resolved. Do you have a status page where I can follow this outage ?
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
How do I know when it has been resolved. Do I need to re run my deployments manually? Where can I get more information about this outage. All my deployments currently stuck
2 months ago
2 months ago
18 hours and counting. Still no deployments 🤦🏻♂️
2 months ago
These container creation failures are on our side, not anything in your service. We've identified the cause and are rolling out a fix for affected services, though we don't have an ETA yet. Failed deployments won't rerun automatically, so once the fix reaches your service you'll need to trigger a redeploy, and that succeeding is how you'll know it's resolved. Platform-wide incidents are posted on our status page, but since this affects a subset of services we're tracking it here and will follow up in this thread.
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
how will I know when it is fixed
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
You'll know it's fixed when a fresh deployment of this service completes successfully. The failed deployments won't retry on their own, so once the fix reaches your service you'll need to trigger a redeploy, and that succeeding is how you'll confirm it's resolved. We're tracking this on our side and will post in this thread once the fix has landed for your service, so you don't have to keep checking manually.
Status changed to Awaiting User Response Railway • 2 months ago
2 months 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 • 2 months ago