Deploy stuck on Build step
I migrated a volume from the US-East to US-West region, then changed the connected service's region from US-East to US-West, and now the deploy keeps hanging/getting stuck on the Build step.
Any ideas what might be happening? 
29 Replies
Project ID:
c53c304a-2798-4291-ab2d-70171bc7f914c53c304a-2798-4291-ab2d-70171bc7f914
Service id is 4e6d359e-fd5f-4b08-8d57-2a51c6546017
usually you move the service so the volume follows it automatically, but you did it backwards
Errr on second thought
I think I actually did move it from the service. It told me that it would migrate the volume as well? π€
Since the volume follows the service region?
welp this is a bug, but its now the weekend
Yeah not mission critical.. so it's all good. Just wanted to report the issue π
I wish there was a way to select a specific region when deploying services. Would make my life alot easier lol π
team is talking about a global setting on your account instead
Hmm I think a per project/service selector would be more beneficial no? I think alot depends on what the project is for. Like maybe I have a special use case where I want the app to be in US, or EU. I think having a region dropdown would be great π But would be curious how others felt about it as well
Having to swap back and forth in a global setting seems weird
i said both
Yeah or both would work too
set the global setting, for what youre most likely to deploy to, then have an option on template deploy to pick another region if need be
Yeah for sure! Global setting prevents having to change the region every time you deploy (for example EU folks), but the per service/project selector for those who want to change from the default π
saves them costs on moving data from one region to another
Yeah i've been having to swap regions at the moment.. it's a pain 
when deploying a template π
when deploying a template πwhy swap from US-East to US-West? you where swapping back to the default region??
The default is US-West for me
so I wanted US-East
you said east to west lol
Right.. this is another deployment
even so, youre just testing, whats wrong with leaving the tests in their default region?
This issue is related to the Prometheus service I deployed today
Which I think I went from US-West -> US-East, but then now back to US-West π
I'm leaving things in US-West going forward from now yep
I'm just curious, why swap west -> east -> west?
I don't remember why I swapped it from US-West to US-East tbh
I'm wondering that myself
I think maybe I forgot I deployed the rest of my services to US-West?
Would be cool to have like a region flag at the top of each service box π
Errr, like flag + region code or something
that would be cool
Leave it up to me to find a bug right before the weekend that causes me not to be able to deploy
you're not the first
What's the protocol for if i'm in this situation with like a prod app? Would I still have to wait or.. any way to push stuff through over the weekend or?
for hobby users, nothing, for pro users (yourself) I don't actually know
We flagged this internally but itβs outside working hours for the team + holiday availability
If itβs causing a production level issue let us know but we can pick this up first thing come Monday
Not a production app, so waiting until Monday is perfectly fine! Thank you π