I observed for local execution, when the agent (and local thread performing the flow) get interrupted, the flow run that was Running is 'lost'.
There's nothing actually performing the flow run anymore because it was terminated. That flow run is no longer on the queue and no more agent picks it up. It can never leave the 'Running' state, but really we wanted some agent to attempt this again.
@Christopher Boyd I think that's what the other Prefect user on
Github Issue 7116 is also seeing, but with Kubernetes.