Hi All! Currently, I am using

prefect==2.19.9

with a self-hosted Prefect server. When a Prefect flow runs as a pod in a Kubernetes cluster and the pod gets removed due to a reboot, the flow’s state remains perpetually in the “running” status. How can I resolve this issue?

there's no solve for this probably, we run a flow which checks all the running flows and marks them cancelled if they have exceeded the time it should have taken

Hi Shelley and Ankit! Upgrading to version 3.1.8 of Prefect should help you out with this. It introduces flow run heartbeats to prevent flow runs from getting stuck in

RUNNING

due to infrastructure failures. There's instructions for setting this up in the link

@Bianca Hoch Awesome feature! thanks!