Forum Discussion

sarah_riecke's avatar
sarah_riecke
Regular Visitor
6 months ago

Databricks Queries NOT Hitting Databricks

I have a report published in the service that connects to Databricks.    About a month ago we were getting a timeout error, BUT the queries sent from databricks weren't hitting the serverless sql w...
Need Help
v-sgandrathi's avatar
v-sgandrathi
Icon for Community Support rankCommunity Support
5 months ago

Hi sarah_riecke,

 

Thanks for clarifying. Since the Power BI refresh starts only after the ADF pipeline finishes and the notebooks run on clusters separate from the SQL Warehouse, it seems unlikely there is direct compute contention between the notebook tasks and the warehouse.

Because no queries show up in SQL Warehouse monitoring, it appears the Power BI Service connection isn’t reaching the Databricks SQL endpoint during the failed refresh attempts. The fact that the refresh works later in the day suggests the issue might be due to environment conditions at the time the pipeline triggers the refresh, rather than a configuration change.

It may be helpful to check if multiple pipelines or automated refreshes run around the same time. Even across different workspaces or projects, simultaneous API-triggered refreshes can cause connection delays in Power BI Service. In these cases, the dataset refresh may keep retrying, but the request never reaches Databricks SQL Warehouse, explaining the lack of query history in the logs.

Also, confirm that the SQL Warehouse is fully started when the API refresh request is sent. If it’s still starting up, the connector could retry several times before timing out. Since the refresh later in the day works, it’s possible the warehouse is already active then.

Reviewing the Power BI dataset refresh history and capturing the Activity ID for failed runs may help determine if the issue happens during the initial connection stage. If possible, try triggering the refresh a few minutes after the pipeline completes or run a small validation query against the SQL Warehouse before calling the Power BI refresh API. This can help confirm if the problem is related to warehouse readiness or connection timing.

When automated refresh fails but manual refresh later succeeds, it’s usually due to timing or connection initialization on the service side, rather than an issue with Databricks compute, especially when no activity is recorded in warehouse monitoring.

 

Thank you.