a day ago
Hey everyone,
Hoping someone's run into this or has a fix. I recently upgraded from the trial to the Hobby plan and created a new project ("Anchor AI"). Every single deployment since then has been stuck at "waiting for build to start" and just... never progresses. No build logs at all — not in the CLI (railway logs -b says "Deployment does not have an associated build"), not in the dashboard either.
Things I've tried, all with the exact same result:
My real app's Dockerfile
A trivial one-line test Dockerfile (RUN echo "hello") — should build in seconds, still hangs
Deleted the whole project and made a fresh one — same problem
Switched the service region from us-west to us-east (railway scale us-east=1 us-west=0) — same problem
Since it's happened across two separate projects and two different regions on the same account, it really seems like something account/workspace-level rather than project- or region-specific — maybe tied to the trial→Hobby upgrade?
I saw a couple of threads here that sound similar and might be related:
"Workspace build limit stuck - 0 active builds but all redeployments fail"
"Service stuck on full builder us-west1-7lx0 due to ResourceExhausted (no space left)"
Details if it helps:
Original project: a187495f-904f-46ff-8027-37626cd682c5 (deleted) — deployments 9c06e838, 930f4862, 2b860b88, a70549fa
New project: 7ebc19ce-df2e-4123-9444-aac6a294506b — deployments d84681d0 (us-west), 8a0c78fe (us-east)
Account: support@anchorcloud.org
5 Replies
Status changed to Awaiting Railway Response Railway • 1 day ago
a day ago
Hey!
Is it alright if i try to trigger a build to test this? Would love to see it live
Status changed to Awaiting User Response Railway • 1 day ago
noahd
Hey! Is it alright if i try to trigger a build to test this? Would love to see it live
6 hours ago
Go ahead and trigger a test build.
Status changed to Awaiting Railway Response Railway • about 6 hours ago
Status changed to Solved anchorcloud1 • about 6 hours ago
Status changed to Awaiting User Response dizzydes90 • about 6 hours ago
6 hours ago
I see you marked as solved, did things improve?
Looks like your deploys were dying while the code upload is still in progress, before a build ever starts. That's why there are no build logs and the CLI says no build exists. Every failed attempt timed out at exactly 15 minutes mid upload, on both projects and both regions, so this isn't your account or your plan. This will be hard to copy on our side but this might help:
So railway up uploads your entire project directory, not just the Dockerfile, so the one line test didn't change what got sent. Could you run railway up again and share the upload size the CLI prints? If the folder is heavy, a .railwayignore file (same syntax as .gitignore) excluding things like node_modules, virtual envs and model files could help, there's a possibility this is due to a large size.
Let me know how it goes.
dizzydes90
I see you marked as solved, did things improve? Looks like your deploys were dying while the code upload is still in progress, before a build ever starts. That's why there are no build logs and the CLI says no build exists. Every failed attempt timed out at exactly 15 minutes mid upload, on both projects and both regions, so this isn't your account or your plan. This will be hard to copy on our side but this might help: So railway up uploads your entire project directory, not just the Dockerfile, so the one line test didn't change what got sent. Could you run railway up again and share the upload size the CLI prints? If the folder is heavy, a .railwayignore file (same syntax as .gitignore) excluding things like node_modules, virtual envs and model files could help, there's a possibility this is due to a large size. Let me know how it goes.
4 hours ago
Hey, sorry for the late response.
i marked it by mistake and i just noticed it right now
i apologize for this mistake.
Status changed to Awaiting Railway Response Railway • about 4 hours ago
3 hours ago
No worries, if you get a chance to try the flow above please update.
Status changed to Awaiting User Response Railway • about 3 hours ago