Hello,
I am attempting to schedule a workflow that contains a Databricks Simba Spark ODBC connection to run on Alteryx Gallery. I have created connections using both the Input tool and the Connect In-DB (with Data Stream Out tools) that run successfully -- as long as the databricks cluster is active.
When attempting to run with an inactive cluster, the workflow fails (with both types of Input tools) and I receive the error:
Error SQLDriverConnect: [Simba][Hardy] (34) Error from server: Bad Status: HTTP/1.1 503 Service Unavailable.[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
This will kick off and activate the Databricks cluster, despite not running the workflow. If I run the workflow again (after the cluster boots up ~5 minutes later), it will run successfully.
My question: does anyone know a way to start a databricks cluster via Alteryx, without having to schedule a workflow that will end in error?
Interesting. Are you running DB on Azure or AWS? I haven't seen this issue on DB on AWS. Can I ask what you SQL endpoint looks like in your ODBC 64 HTTP Path? What happens if you increase your socket timeout in the ODBC 64?