Hey!

Is it alright if i try to trigger a build to test this? Would love to see it live

Go ahead and trigger a test build.

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.

Hey, sorry for the late response.

i marked it by mistake and i just noticed it right now

i apologize for this mistake.

No worries, if you get a chance to try the flow above please update.

Hey, thanks for looking into this. Ran railway up --verbose and got the exact size: 34,964,643 bytes (~33.4 MB) after tightening .railwayignore to exclude venv, model cache, and other heavy files.

Unfortunately, it still failed the same way — stuck at "waiting for build to start," then failed after roughly the same ~15 minute window. So even at this much smaller size (down from over 80MB before), the upload/build still never completes. This makes me think it might not purely be about payload size — possibly something about the upload throughput itself timing out regardless of file size.

As a workaround, I've also set up a private GitHub repo with the same code and I'm trying to connect the service to deploy from GitHub instead of CLI upload (railway service source connect), but I'm getting "User does not have access to the repo" — still working through authorizing the Railway GitHub App for the account. Will update once that's sorted, but wanted to share this data point in the meantime.

and sorry for the late response.

At 33 MB the upload should finish well under 15 minutes, so payload size is ruled out. Deploying from GitHub is a good next step since it skips the CLI upload path entirely. For the repo access error, go to GitHub Settings > Applications > Railway App > Configure > Repository access, and grant it access to the private repo. Then unlink and relink the GitHub integration from your account settings.

Hey, i apologize for the late response,

i just want to say thanks for your support and for your time, and finally my AI Model (Anchor AI Fathom-1) is deployed.

Thank you.