scale or autoscale doesn't keep instances in the primary region

[ignoramous]

Personally, I’d disable autoscale as it has been on life-support ever since Fly shifted its focus to Apps v2 (aka Machines).

@luizkowalski

Is there a way to ensure that when scaling it, fly keeps instances on the primary region as much as possible?

I don’t know what primary_region means in the context of regular Fly apps (I thought it only holds meaning for Fly-automated Postgres)… but something similar has been asked and answered before:

Scaling not prioritizing primary region

Unfortunately, Nomad makes it difficult to do things the way you’d want (which is also the way we want). You can’t autoscale AND spread things evenly around regions. You can manually fly scale count X --max-per-region=1 to make sure VMs are evenly distributed, but it won’t work with autoscaling.