# Cannot deploy app since yesterday

**URL:** <https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676>\
**Category:** General\
**Tags:** login-only\
**Created:** [August 8, 2023, 2:21pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676 "2023-08-08T14:21:33Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![wjordan](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wjordan/32/1280_2.png) [@wjordan](https://community.fly.io/u/wjordan)\
**Post date:** [August 9, 2023, 6:45pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/13 "2023-08-09T18:45:52Z")

</div>

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](https://fly.io/docs/reference/app-availability/#standby-machines-for-process-groups-without-services) 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](https://community.fly.io/t/flyctl-versions-autoupdating-and-the-cli-apocalypse/13794) first) to work around this issue:

 

```auto
flyctl settings autoupdate disable
curl -L https://fly.io/install.sh | sh -s -- v0.1.71

```

  Sorry for the inconvenience! I hope this resolves your issues.

---

_[View the full topic](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676)._