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

Dear all,

I just now got the following error:

```Unexpected error: OSError("Timed out trying to connect to '<tcp://10.100.0.100:44991>' after 10 s: Timed out trying to connect to '<tcp://10.100.0.100:44991>' after 10 s: connect() didn't finish in time")```
Is this a known issue?

The environment is a daskkubernetes cluster running on AWS EKS...

Hi <@U0176BCNXEV> ! Can you provide a little more context to this error? Where did this show up etc

It shows up when trying to run a flow:

```Submitted for execution: Job prefect-job-5bf53878

Adaptive scaling started: minimum=100 maximum=100

Beginning Flow run```
Then, the error message shows up

Afterwards, the dask pods are deleted

```Deleted pod: dask-root-cec0f0d6-6zbxsc```
and the flow is restarted:

```backend_accure_net restarted this flow run```

Got it - is this running against Prefect Cloud or Server?

Thanks <@U0176BCNXEV> - this _looks_ like an issue with your Dask cluster; can you confirm that your cluster is up and healthy in those situations?

Oh, I abused the number 1 rule of debugging:

&gt;  Have you tried turning it off and on again?
Uploading the flow again solved the problem...

:smile:  no worries! Let me know if you run into that again