Deployment Failing on Free plan with no log
rduan1228
FREEOP

6 hours ago

I’m trying to redeploy my discord bot after the major outage a few days ago, but it keeps failing with “Deployment failed” and no logs. "Running a diagnosis to find out why" doesn’t return anything either. The bot was deployed and running fine before the outage, and I haven’t changed the code or any settings. Without logs, it’s hard to figure out what’s wrong. Is Railway still down in certain regions, like US-West?

Awaiting Railway Response

2 Replies

Railway
BOT

6 hours ago

Your latest deployment failed before the build started, at the step where we retrieve your service's source code, which is why no build or deploy logs were produced for it. Nothing in that failure points to your code or settings.

On regions, we have no open incident affecting deployments in US West. The recent EU West (Amsterdam) deployment incident was resolved on October 25.


Status changed to Awaiting User Response Railway • about 6 hours ago


Railway

Your latest deployment failed before the build started, at the step where we retrieve your service's source code, which is why no build or deploy logs were produced for it. Nothing in that failure points to your code or settings. On regions, we have no open incident affecting deployments in US West. The recent EU West (Amsterdam) deployment incident was [resolved on October 25](https://status.railway.com/incident/FM0QZ3B1).

rduan1228
FREEOP

4 hours ago

Thanks for checking. I’ve already tried reconnecting GitHub in Railway and checked the repo access on GitHub, and everything looks right every time. The service is also pointed at the correct repo and branch, and nothing about either has changed. Is there anything else on your end that could be causing the source retrieval step to fail?


Status changed to Awaiting Railway Response Railway • about 4 hours ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...