25 days ago
Project: Telegram Staff Monitoring System
Service: worker
Environment: production
Region: US West
Issue:
Deployment has been stuck at CREATE_CONTAINER stage with two consecutive failures.
Failed Deployment IDs:
7d8066c1-37f6-438d-869b-ebe7710bab95 (current, stuck 10+ minutes)
1040fecd-1930-458c-b07d-182506ec4966 (previous failure)
Build Status:
✓ SNAPSHOT_CODE - Success
✓ BUILD_IMAGE - Success
✓ PUBLISH_IMAGE - Success
✗ CREATE_CONTAINER - Pending (stuck)
Context:
Same commit (7f270ddf) deployed successfully on June 6
Service has a volume mounted at /app/data
Start command: python monitor.py
Diagnosis tool confirms this is a platform infrastructure issue, not a code issue
Any help would be greatly appreciated. Is there anything I can do on my end to resolve this?
Attachments
3 Replies
25 days ago
Your builds are completing successfully, but the container creation step is failing due to a transient platform-side issue we're aware of and actively working on. This is not something you can resolve from your end. Please hold off on additional redeploys for now, as queuing more can compound the issue, and retry once some time has passed.
Status changed to Awaiting User Response Railway • 25 days ago
Railway
Your builds are completing successfully, but the container creation step is failing due to a transient platform-side issue we're aware of and actively working on. This is not something you can resolve from your end. Please hold off on additional redeploys for now, as queuing more can compound the issue, and retry once some time has passed.
25 days ago
How long will it take to complete, and what are the reasons for this?
Would changing the deployment location to Singapore resolve the issue?
Status changed to Awaiting Railway Response Railway • 25 days ago
24 days ago
Hey, answering your Singapore question directly: don't switch. Your volume is region-bound, so moving the service to Singapore would leave your /app/data behind in US West. Not worth it, especially since the underlying issue is now resolved.
What happened: container creation was failing on a subset of US West hosts June 11-12. Your builds were fine, the hosts just couldn't start containers.
Redeploy in place and it should go through with your volume intact. Reply here if it sticks at Create container again.
Status changed to Awaiting User Response Railway • 24 days ago
17 days 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 • 17 days ago