So, always is a good restart policy for always-on Machines. It’s not a good restart policy for Machines you stop yourself and would like to stay stopped*, or Machines, with services, that exit when idle so that Fly Proxy can wake them on request, which is closer to the generic web app use case our default fly deploy expects to be most common.
I’m not saying we nailed the UX on this one 
. It will improve, on several fronts! Just thought it might be less mysterious with that info.
*In fact I missed that the restart policy is about whether to try to get a Machine up and running again without reaching the stopped state, so if you stop a Machine, it’ll stay stopped unless the Fly Proxy wakes it up.