outer nymph
Hi! Trying to deploy something and the build... less than a second, which is brilliant. However, it's been stuck on deploying for 15 minutes, which is... less than admirable.
This has been happening quite a bit over the last few days - is there any reason for this?
9c62e56a-8604-43b5-b196-4fb4be21ea8d
dark oysterBOT
outer nymph
I guess more specifically, it's the "Publishing image" phase right now
Well, it just deployed, after 18 minutes. Leaving this up as it's still a massive jump from previous deployment times
dawn hedge
i have the exact same issue
dire latch
++
dawn hedge
other peeps in gen chat were having the issue as well
storm depot
same here
past linden
You guys still having this problem?
outer nymph
You guys still having this problem?
Yes
Insane deploy times after builds, compared to what they were like before
And the build is taking less than a second, with publishing taking less than 3 seconds
So it's baffling why it's taking ~10 or more minutes to deploy
past linden
A fix for this was deployed about 11 hours ago, how big is your image?
outer nymph
A fix for this was deployed about 11 hours ago, how big is your image?
Can confirm - they're working great now! 😄
But yeah the image was 49.85MB, so not that large at all
past linden
oh awesome
pseudo ocean
same issue here for my Postgres database :(
all the other services are taking less than 3 mins, but this one is already 11 mins
btw, I'm using the Chatwoot Template
radiant oceanBOT
New reply sent from Help Station thread:
Hi! Same issue. Postgres DB is being deployed for 1 hour... And it's still deploying
You're seeing this because this thread has been automatically linked to the Help Station thread.
radiant oceanBOT
New reply sent from Help Station thread:
Hi I''m having the same issue. I have been trying to cancel and redeploy but have not been able to deploy since it goes up to 20+ minutes
You're seeing this because this thread has been automatically linked to the Help Station thread.
past linden
Hey, there is currently an ongoing incident regarding this, you can follow it here:
https://status.railway.com/cma2xgdyx001s172fcvs2e7e9
tacit nova
We are still investigating the cause, sorry for the inconvenience!
tacit nova
We have resolved the incident, if you have any in-flight deploys you will need to cancel and redeploy them.
tacit nova
We have since added more capacity in all regions and updating our monitoring to let us know long before this ever happens again.
tacit nova
!s