Forum Discussion
Vague Refresh Failure message: We're sorry, an error occurred during evaluation
- Anonymous1 year ago
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.
Hi jakaihammuda
That message is the generic Mashup/Evaluation error. Since the next run succeeded, it was likely transient. Quick, practical checks:
-
Timing/cluster: Databricks warehouse/cluster may have been asleep. Start it 5–10 mins earlier or shift the refresh time.
-
Auth blip: Re-enter dataset creds (PAT/Entra) and confirm expiry.
-
Capacity spike: If on Premium/Fabric, check Capacity Metrics around the failure time; avoid overlapping heavy refreshes.
-
Find the culprit step: Refresh history >> View details to see which table/step failed; test that step in Desktop.
-
Incremental refresh: Manually refresh the latest partition to isolate issues.
-
Gateway (if used): Update gateway, check logs for that timestamp.
If it happens again, grab the Refresh ID and match it to Databricks query history for that minute this usually pinpoints the cause.
- jakaihammuda1 year ago
Helper III
Thank you! Will take this on board and perform some checks 🙂