I have the same exact issue. Containers without Prisma deploy fine, but the ones that have a pre-deploy command have been deploying for like 15 minutes now.

Have you reported this to railway privately?

I'm unable to do so, given my Hobby plan.

What? You can't make a private report to Railway unless you're on Pro? That seems like a great decision by them...

But no, I haven't reported it privately. Looking through the threads it seems that they're pretty overloaded right now and I'm not sure if a private support ticket would help. Also, I'm lucky that all services that have this issue still have an active container, so I'm not having any downtime.

If you want I can create one for both of us and then link this thread. Hopefully they'll see this thread soon and fix the issue.

Also, 25 minutes and counting, services are not deploying.

Edit: Service successfully deployed after 38 minutes. But I'm not sure if they actually fixed it or if that is how long it will take for every deploy.

Thanks for keeping me posted!

No worries.

Seems that there was a different thread opened about this issue a few hours ago, but doesn't seem really resolved to me (except that we should just wait for it to finish): https://station.railway.com/questions/predeploy-stuck-e9172bf0

It says we should use npm run prisma migrate deploy && exit

exit command at the end.

I think that the "exit" command was just added by the OP and isn't necessarily the solution.

And even if that solves it, that is completely unacceptable because it worked before without "exit".

npx prisma db push --accept-data-loss && npm start
and faith kkk

Yeah it seems that faith is all that is left after what happened today.

Absolute disaster

And even found another thread: https://station.railway.com/questions/simple-prisma-pre-deploy-command-runs-fo-16600b39

Hello,

This should be resolved. We are seeing pre-deploy commands finished successfully across the board now.

Currently on 4+ minutes to go from finishing the pre-deploy command to it being live (health check will be near instant). Deploy id: 7081c1a2-ed48-4ccf-9e01-785b8450a05c

This is why I'm scared to deploy to my prod environment because if I have DB migrations, there will be an unknown period of time where my backend and DB are out of sync.

EDIT: Now 10+ minutes. It is not resolved.

Hello!

We're acknowledging your issue and attaching a ticket to this thread.

We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.

Please reply to this thread if you have any questions!

Hi! I just confirmed your deployments completed. Really appreciate your patience while we worked through this. Future deploys should gradually return to normal durations as recovery finalizes.