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

Hi All - I started with a flow with prefect cloud which seems to have paused for ~2 hours. When I look at the dask scheduler, there are no reported tasks remaining. Is there any reason why my flow would have stopped?

Hey <@U01AQF76WT1>, this is weird for cloud. I normally see this behavior in server because workers are not configured to hit the correct API (they hit cloud instead of server). The most basic check would be to check is the Dask workers are hitting Prefect Cloud (are any tasks finishing successfully?)

Is it paused or stuck in a running state? (we have a paused state)

I would suggest looking at the Dask dashboard and seeing if there were any memory issues?

Indeed this is strange. The flow is halfway complete, and has halted in a running state. When I look at the scheduler UI, there are are no tasks that are queued or running. :confused:

I have seen this once where there was an error in the code and the error just wasn’t being raised.

I know that if I resubmit the the flow. It will likely get pass this point. It is not the ideal solution though.

I will resubmit my flow again, but this has happened on more than one occasion. My flows tend to be to very large parallelized runs.