"could not wake up machine due to a timeout requesting from the machines API" after the app has already un-suspended

[mayailurus]

Hi… Three other fellow users mentioned very similar anomalies recently:

https://community.fly.io/t/another-one-for-persistent-machine-still-attempting-to-start-errors/26064

There hasn’t been a resolution yet, that I know of, but here’s a work-around that was recommended back then:

@Sam-Fly

We’re continuing to investigate the cause of these. From what we’ve seen, it seems to impact a small number of machines when waking from a suspended state. As such, changing your app to use a stop instead of a suspend should avoid them altogether.

Hope this helps a little!