Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

hey =] couldn’t find a clear explanation in the docs - what could be a reason for me to get a `task is already running` (for a KubernetesRun)? and then `Finished task run for task with final state: 'Running'` …. (other than that, it seems like the task doesn’t really run.

Hey <@U02DFBS9E9M>, this is weird. Are you on a DaskExecutor?

image.png

The UI shows that the flow FAILED since the task seemed to return `None` which shouldn’t happen in any reasonable scenario of the flow (I’m expecting a tuple)

It seems like an OOM is happening, I’m not sure where though:

also, after 10minutes, I’m getting this (the flow status is FAILED long before that, though)

also, we are using a `LocalExecutor` , not really sure what that means :X

<@U01QEJ9PP53>, thanks for your help :slightly_smiling_face:

Ah that does look like your container is running out of memory.So Prefect has heartbeats which check if your Flow is alive. If the underlying infrastructure crashes and the heartbeats die along with the Flow, the UI may show it as running for a while until the Zombie Killer marks it as failed.