We used the syd region where I see that some problems were reported.
I already removed the region temporarily and did the deploy again but the error continues.
Does your release command end? I assume it does, but maybe it’s stuck doing something forever like a database transaction that wasn’t cleanly halted (and thus is holding a lock).
You can check fly status in a different terminal if you want to see what’s happening with your instances. You can also fly logs and you should see new instances’ logs coming up.
This usually happens because there’s a conflicting scale/regions config.
Did you set fly scale count 3 --max-per-region 1 by chance? If you only have two regions, and want three VMs, it can never fulfill that. Assuming that’s the case, you can either add a region, or run fly scale count 2 --max-per-region=1.