13 days ago
Project ID: 9ec075d4-f95e-4813-8393-2de8e4fbecc6
Deployment ID: 0d437b00-0a68-4a3f-8e2b-c8be6d107e53
The deployment was created at 2026-08-07 17:45:08 UTC and failed at 17:58:51 UTC after 13 minutes 43 seconds.
Failure stage: SNAPSHOT_CODE
Error:
/orchestrator.BuildService/StartSnapshotAndBuild UNKNOWN: failed to start workflow: context deadline exceeded
There are zero build or deploy logs because the workflow never reached repository snapshotting. The deployment is marked FAILED, but redeploy requests continue to return:
“Cannot redeploy yet, please wait for the original deployment to finish building, then try again.”
The previous production deployment remains online. Please clear or repair the stuck orchestrator state so the latest main commit can deploy.
1 Replies
Status changed to Awaiting Railway Response Railway • 13 days ago
13 days ago
A deploy workflow on ai-radar-web failed internally before it ever reached the build stage, and the failure left the service still holding its build lock. That is why every redeploy came back with "Cannot redeploy yet, please wait for the original deployment to finish building." Nothing in your repo, your config, or that commit caused it.
That stuck state has since cleared. The same commit, "Make dashboard authentication optional", is now deployed and active on ai-radar-web, and the service is serving traffic normally, so you should be fully unblocked.
Sorry for the detour here.
Happy building 🚂!
Status changed to Awaiting User Response Railway • 13 days ago
6 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 • 6 days ago