Hey Prefect we re encountering a somewhat stochastic error w

Question

Hey Prefect we re encountering a somewhat stochastic error when running a `wait for flow run` for a long running DatabricksSubmitRun in another flow even when the Databricks job runs to completion without an issue We noticed this can occasionally result in the error enclosed below that causes no heartbeat to be detected Has anyone encountered this Any ideas on what may be causing this and how to address the issue ```Error during execution of task ClientError path flow run message request to failed reason read ECONNRESET extensions code INTERNAL SERVER ERROR exception message request to failed reason read ECONNRESET type system errno ECONNRESET code ECONNRESET ```

Raymond Yu · Answer

In a possibly related note we re also encountering a similar issue polling on EMR termination status via boto3 i e `emr client get waiter cluster terminated wait ClusterId=cluster id ` Where the task also loses heartbeat despite the EMR cluster running successfully and terminating as expected

Anna Geller · Answer

You could disable heartbeat for the subflow this topic dives deeper <https discourse prefect io t flow is failing with an error message no heartbeat detected from the remote task 79|https discourse prefect io t flow is failing with an error message no heartbeat detected from the remote task 79>