1. Temporary resource scarcity (compute, network bandwidth, or concurrency limits on the warehouse) can lead to queries taking longer than usual or connections being dropped unexpectedly—even for small queries.
2. The errors reference Thrift/ODBC, suggesting the issue may sometimes be within the gateway (Power BI Gateway) or driver stack, especially if running locally or in a virtualized environment. If Power BI or its Gateway has been restarted, updated, or is over-utilized, driver sessions may drop unexpectedly.
3. Occasional Azure or AWS cloud maintenance or network events can disrupt serverless Databricks endpoint connectivity. These are typically short-lived but may cause the symptoms you see.

Short-Term Troubleshooting

• Review Warehouse Event Logs: Look for corresponding error or warning events around query timeout and Power BI access attempts.
• Monitor Network Health: Use network monitoring tools or test manual ODBC connections from the Power BI host to Databricks to rule out endpoint or internet issues.

Longer-Term Mitigation Steps

• Increase Client Timeout Settings: In Power BI (and Databricks), raise query and inactivity timeout thresholds to tolerate brief network or resume delays.
• Schedule Warehouse Warming: If feasible, start the SQL Warehouse ahead of scheduled Power BI refreshes to guarantee readiness.
• Update Drivers/Gateways: Ensure you have the latest ODBC driver version and that Power BI Gateway is up to date and healthy.
• Review Regional Status: Check with your cloud provider for any announcements or incidents in the target region.