4 months ago
Service is experiencing repeated container creation failures despite successful builds and image publication.
Details:
Service ID: dd783375-c9ec-4c82-9ea5-87d3da2863df
Environment: production (c8bff6b4-886a-48bb-a632-7af933c64e70)
Project: dazzling-compassion (34f5f5f4-2777-4c4f-a9a9-67b5ace20d4c)
Region: sfo
Failure Pattern:
Three consecutive CREATE_CONTAINER failures since June 12th
Failed deployments:
b08b0514-ba53-43a9-849b-4d008da60f8f (current)
Commits: 37c5552d, 4a78ecac, 87c5a48
Last successful deployment: June 9th (c9897d06)
Build stage completes successfully; failure occurs during container scheduling (~22 seconds after image publication)
Error: "Failed to create deployment"
Code Changes: Application-level only (email notification error handling); no infrastructure or configuration changes.
Request: Please investigate container scheduler availability and resource allocation in the sfo region.
1 Replies
Status changed to Awaiting Railway Response Railway • 4 months ago
4 months ago
Hey Kagiso, this was a platform issue on our side, not your service. Container creation in sfo was failing on a subset of hosts June 11-12, and your three failures landed in that window. The ~22 second failure after image publish is the exact signature.
It's resolved. Redeploy and you should be back. If it fails again, reply here with the new deployment ID and I'll trace it directly.
Status changed to Awaiting User Response Railway • 4 months ago
4 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 • 4 months ago