2 months ago
Project: nurturing-clarity (330bbf55-5483-4a67-ae8a-fa9431875937)
Service: StageTools (a083dd8c-207a-40e6-9328-3073f956a6e9)
Environment: preview (844ca6fc-2381-4601-96f1-423eb852025a)
Three deployments from branch dev are stuck in QUEUED status with zero build/deploy logs, no progress for 25+ minutes:
60abd289-3684-4f6a-8770-dbec053032ec (created 00:06 UTC)
e56f956a-950b-40e6-8239-05c07e82f286 (created 00:15 UTC)
f375335d-8223-4dff-ae3b-b4dbe2620dbd (created 00:21 UTC)
This matches the active incident 'Deployments are slow to progress' (YYU63JUO). Could you please clear/cancel the stuck queued deployments and/or manually trigger the latest one (commit 1807949) so our preview environment can go live again?
2 Replies
2 months ago
Apologies for the trouble. Your three deployments are queued at the platform level (0 of 3 workspace slots are in use, so this is not a concurrency issue on your side), which lines up with an ongoing incident affecting deployments across all regions: Deployments are slow to progress and are prone to timeout failure. You can cancel the two older queued deployments yourself from the service's deployments list and keep or re-trigger the latest one once the incident is resolved.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved dev • about 2 months ago