App build in us-west1 despite region variable being set to europe-west4
Hi, I was wondering why all of a sudden the latency to the DB was jumping up and I just saw in the build logs that the region was us-west1 despite the region variable being set to europe-west4. After removing and adding the variable again it deploys to europe-west4 again, but I wanted to ask whether you are aware of the app suddenly switching regions. We had some very impacted performance because of that.
23 Replies
Project ID:
071f7771-ab05-488c-b53b-47a7ec81aac1
071f7771-ab05-488c-b53b-47a7ec81aac1
I left one service running in us-west1 in case you would like to investigate that, let me know 🙂
im sure the team would, could you provide the service if for that service
There you go: 84de9bb4-bc75-4d4a-baa8-5ce82b841a0f
Thread has been flagged to Railway team by @brody192.
btw. @brody192, you are doing an awesome job and I'm really thankful for the work you do. It goes a long way 🥰
thanks for the kind words 🙂
Raised, we'll look into this. Thanks!
We are blocked from deploying some critical fixes atm. because deploying to US makes our app nearly unusable. Looking forward to a fix 🙌
Does your team member deploying have priority boarding enabled? What happens if someone with priority boarding enabled pushes the deploy?
I'm the one changing it and I have it enabled if I'm not mistaken
@Patrick are you on the pro plan? iirc regions are locked to pro plan atm
You don't have the Discord role
Yes I am, but with an organization I created, not my personal workspace
Understood. Are you deploying this within your org?
Yes, this yellow info box is new and I got the popup to "join priority boarding" when adding the variable but it still worked
Spoke too soon, just wanted to ensure that we've checked all the boxes. Thanks
Pinging @Ray back in here ^
Should I set the region in the service panel now?
I believe so
First deploy with the region set in the panel looks good
Oh that’s out! It should work now. Previously with the env var there’s a “user must be in priority boarding” constraint so if somebody without that deploys, it likely gets ignored
Some Discord thingies are broken on our end 😬
let us know if the deployment goes back to us-west1
Looking good so far 👍