Hi all, we identified a bug in fly deploy introduced a couple days ago (starting in v0.1.72) causing deploys to incorrectly wait on an app’s standby machines to enter the started state (which will never happen, resulting in a timeout error), when they should properly be skipped.
We are working on publishing a new release with a fix (which will be v0.1.74). A new version of flyctl (v0.1.74) has been released with a fix for this issue.
In the meantime, you can manually downgrade to v0.1.71 (after disabling autoupdate first) to work around this issue:
flyctl settings autoupdate disable
curl -L https://fly.io/install.sh | sh -s -- v0.1.71