a month ago
Our develop deployments have been stuck at “Waiting for build to start” for over 5 minutes. (which are normally within 2mins)
The Railway dashboard also shows:
Invalid prisma.workspace.findMany() invocation:
The column Workspace.supportTierOverride does not exist in the current database.
Our application uses Drizzle, not Prisma, so this appears to originate from Railway's internal services.
Could you investigate whether these issues are related?
8 Replies
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
Hey, this seems to be a transient error that should be resolved now. Could you try again?
Status changed to Awaiting User Response Railway • 28 days ago
a month ago
Also, do you mind sharing where you saw that error? Was it in the network tab or some toast message that you received in the dashboard?
ray-chen
Hey, this seems to be a transient error that should be resolved now. Could you try again?
a month ago
It worked! Thanks for the quick reply.
This error was from the deployment details. (build logs)
Before this error occurred, the dashboard showed “Derailed,” and I couldn’t log in.
I wasn’t able to log in for about 5 minutes. After I was able to log in again, the deployments were still failing, but now everything is working fine.
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
i am having the same eror too
a month ago
Failing for me aswell... worth noting my stack is different from OP's: this is a Python/FastAPI service (python@3.12.14), no Node, no Prisma, no Drizzle. So this isn't stack specific on the user side
Status changed to Awaiting User Response Railway • 28 days ago
a month ago
I tried redeploying, but it kept failing with the same error. I deployed a new commit, and it deployed successfully this time.
Status changed to Awaiting Railway Response Railway • 28 days ago
Status changed to Solved brody • 28 days ago