Why flyio create 2 "app" machines?

Good afternoon. Fly deploy for some reason began to behave in a strange way during deployment. The fact is that I can’t have two simultaneously working machines and before deploying I always do fly scale count 0. But now, after the defield, fly for some reason creates two machines that start to conflict with each other when using the telegram api. In general, can I explicitly tell fly not to create two machines when deploying? Thank you in advance!

Process groups have changed. This will:
 * create 2 "app" machines

fly deploy --ha=false

1 Like

@pb30 already posted an answer there but here is the reasoning → Increasing Apps V2 availability

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.