503 Error from Databricks when Cluster Inactive/Starting Up via Alteryx

[zbowden2010]

Hello,

I have been connecting to Databricks via Alteryx. It works fine when our cluster is active, but returns a 503 Service Unavailable error if the Cluster is inactive/starting up. I have previously reached out to Alteryx, but they have told me this is related to how our Cluster in Databricks is configured.

Can someone provide guidance on how Databricks clusters need to be configured in order to prevent a 503 error from being sent when the cluster is booting up?

Thank you,

Zach

[zbowden2010]

I should have mentioned in the original post, we are using Microsoft Azure and a Simba Spark ODBC Driver.