a month ago
know this has been asked a few times, but out of all of the threads, I found no real answer.
I am on the Hobby plan and have been trying to deploy for the past hour and it gets continuously stuck at the "Initializing" status with this deployment message: "Deployment in progress: Taking a snapshot of the code... "
I've read the deployment docs and I'm aware it states that in instances of high server load, Pro/Enterprise plans are prioritized. Understandable.. However the docs state that it would show a "Limited Access" notice in the dashboard - I'm not seeing that anywhere. After 45 minutes of it sitting at initializing - and then eventually canceling the deployment and trying again, with it now being at 20 minutes, I'm just not sure what's happening.
If the deployments truly are in a queued state, it is absolutely horrible UX to show the deployment status as "Initializing". It obviously insinuates that it is actively trying, but yet no build logs or deploy logs are present.
Am I missing something?
2 Replies
a month ago
I just hit the same issue this morning, super frustrating. I haven't been able to figure out any workarounds yet, but I've got several passing the 30min mark still in "taking a snapshot of the code".
a month ago
We found the bug on our side, sorry for the trouble. Your service has the "Try Railway Express (Early Preview)" flag enabled, and Express currently only works for services in US West. For any other region, the deploy fails right away behind the scenes but the dashboard never shows the failure, so it sits at "Initializing" forever.
To fix it: open the service's Settings, find Feature Flags, turn off "Try Railway Express (Early Preview)", then redeploy. GitHub deploys will work normally again after that.
Railway Team
Status changed to Solved sam-a • about 1 month ago