Potential Bug: Service Moved to Metal Beta, Region Changed Unexpectedly

I am writing to report a potential bug I encountered while working on a project. Upon deploying a fresh instance, a service unexpectedly moved to the Metal Beta environment and changed regions from US East to US West.

This resulted in the following build error: "Users can only deploy to a single region. Please create a team to deploy to multiple regions."

I was able to resolve the issue by manually swapping the Metal Beta instance back to the US East region. However, this unexpected behavior suggests a possible default setting or hardcoded region within the Metal Beta environment.

I am currently on the Hobby priority boarding plan. Please let me know if you require any further information or clarification.

Thank you for your time and attention to this matter.

Solved

4 Replies

cb6291fc-24eb-46e5-9931-208794305527


a year ago

thank you for reporting, we are going to look into what could have caused this


a year ago

update, it was a bag config setting during our migration of hobby workloads to metal, we have since fixed the issue.


a year ago

!s


Status changed to Solved brody about 1 year ago


Loading...