23 days ago
Hi Railway Support Team,
I'm experiencing a persistent container scheduling issue with my service whatsapp-bot in the us-east4-eqdc4a region that has been ongoing for over 24 hours.
Problem Description: The deployment process completes successfully through all build stages (SNAPSHOT_CODE, BUILD_IMAGE with all 7 Dockerfile steps passing, PUBLISH_IMAGE), but the CREATE_CONTAINER step enters a "pending" state and never completes. The container is never actually created, and the deployment eventually times out and is manually cancelled.
Timeline:
Last successful deployment: May 20, 2026 at 17:44 UTC (commit ef9324a)
Failures began immediately after on the same commit
Issue persists across 6+ consecutive deployments spanning multiple different commits
Problem occurs regardless of code changes or builder configuration
Failed Deployment Details:
Most recent failed deployment ID: f2cee4cc-fc05-4add-8a87-31b3d1476608
Service: whatsapp-bot
Region: us-east4-eqdc4a (iad)
Project: resilient-vision
Environment: production
Build Evidence:
Build logs show zero errors
Image is successfully published: sha256:9a6d9c76006001354a540deae82a80aaeb8576a956a3cc9a1a1cc15a52f43859
Zero CPU and memory usage recorded, confirming container was never started
Analysis: This is clearly an infrastructure-level container scheduling issue, not a code or configuration problem. The build proves the code and Dockerfile are valid and working correctly.
Could your team investigate the container scheduling for this service in the us-east4 region?
1 Replies
23 days ago
Your analysis is correct - the build completes successfully and the issue is at the container creation/scheduling stage. Your service's latest deployment is still stuck in DEPLOYING with no runtime logs, confirming the container was never started. This is a platform-side infrastructure issue currently affecting a large number of deployments, and our team is actively working on it. We recommend cancelling any queued deployments and waiting rather than redeploying, as additional deploys can compound the issue.
Status changed to Awaiting User Response Railway • 23 days ago
16 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 • 16 days ago