Forum Discussion
Helper IIIVague Refresh Failure message: We're sorry, an error occurred during evaluation
Hi jakaihammuda ,
Thanks for checking on this further.
The “Change Data Source” option being greyed out usually means the connection is defined in the M code rather than exposed through the connector dialog, so the command timeout setting cannot be adjusted from the UI.
It is also important to note that the Command Timeout option is only supported in the SQL Server connector. For other connectors, including Databricks, the setting does not surface in the same way.
You can see a related discussion here: Timeout constantly when refreshing.
For Databricks, the practical options are to review query performance and, if needed, configure the STATEMENT_TIMEOUT parameter on the Databricks side. Power BI Service will still enforce its own refresh limits.
Since the issue seems related to the startup time of the serverless warehouse, you may want to test with a provisioned SQL warehouse or keep the warehouse active to avoid the initial delay.
Hope this helps. Please reach out for further assistance.
Thank you.
Super UserHi jakaihammuda
This error generally indicates a connectivity or evaluation timeout issue between Power BI Gateway and the Databricks source. Addressing gateway health, query optimization, privacy settings, and retry logic are the top approaches. Since the error is intermittent and resolved by the next scheduled refresh sometimes, transient network/service issues are likely at fault.
Quick Fixes:
- Check Gateway & Network : Ensure the Power BI Gateway is online and can connect to your Databricks source without interruptions.
- Verify Credentials and Privacy Settings : Double-check that the credentials used in Power BI Service for Databricks are correct and that the privacy level is set appropriately (usually “Organizational”).
- Optimize Queries and Increase Timeouts: Review your queries for performance. If possible, increase any timeout settings to avoid premature refresh failures
- Retry & Monitor Refreshes: Since this error can be transient, monitor scheduled refreshes and manually retry if needed.
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
Helper IIIThanks grazitti_sapna! Does either yourself or rohit1991 know if it is possible to increased a timeout limit in the report or on Service for Databricks Serveless Warehouses? As i think our problem is with the fact that sometimes it can take up to 30 seconds for the warehouse to actually start
- grazitti_sapna
Hi jakaihammuda
You can try the following steps to address the timeout limits in Power BI Service or within your report to see if it resolves the issue
- Power BI Service itself has a hard timeout limit of 2 hours per refresh for Pro licenses (longer for Premium)
- Within Power Query (Power BI Desktop), you can set a Command Timeout in minutes under Data Source settings → Change Source → Advanced Options → “Command Timeout in minutes (optional)”. This is respected during refresh in Power BI Desktop and often honored in Service but only up to the service limits
- However, this timeout setting is generic for the query execution and does not specifically handle the startup latency of the Databricks Serverless Warehouse
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
- jakaihammuda
grazitti_sapna - I am trying to check on this step you mentioned here:
- Within Power Query (Power BI Desktop), you can set a Command Timeout in minutes under Data Source settings → Change Source → Advanced Options → “Command Timeout in minutes (optional)”. This is respected during refresh in Power BI Desktop and often honored in Service but only up to the service limits
However, 'Change Data Source' is greyed out for me - articles online arent too clear on how to enable. It points ot be any issue with the source step in PQ, but cant see why in my report...or what i need to change
v-veshwara-msftCommunity Support
Hi jakaihammuda ,
Thanks for checking on this further.
The “Change Data Source” option being greyed out usually means the connection is defined in the M code rather than exposed through the connector dialog, so the command timeout setting cannot be adjusted from the UI.
It is also important to note that the Command Timeout option is only supported in the SQL Server connector. For other connectors, including Databricks, the setting does not surface in the same way.
You can see a related discussion here: Timeout constantly when refreshing.
For Databricks, the practical options are to review query performance and, if needed, configure the STATEMENT_TIMEOUT parameter on the Databricks side. Power BI Service will still enforce its own refresh limits.
Since the issue seems related to the startup time of the serverless warehouse, you may want to test with a provisioned SQL warehouse or keep the warehouse active to avoid the initial delay.
Hope this helps. Please reach out for further assistance.
Thank you.
- Within Power Query (Power BI Desktop), you can set a Command Timeout in minutes under Data Source settings → Change Source → Advanced Options → “Command Timeout in minutes (optional)”. This is respected during refresh in Power BI Desktop and often honored in Service but only up to the service limits