Destination-Databricks: creating connector throws timeout

I am using Airbyte to move data from salesforce to Databricks Delta. But I get the following error - Connection is not available, request timed out after 60001ms. Looks like the Airbyte throws an error even before cluster spins up in the databricks. Is there any way to increase timeout?

Are you able to connect to the Databricks using your terminal or other tool?

It’s able to run successfully when cluster is already in running state.

You’re saying know the connector works?

Connector works if the cluster is up before the connector starts using it. If the cluster is not ready. It spins up the cluster and runs the job. It fails while it waits for cluster to be ready

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.