Forum Discussion
Warehouse Fabric GUI does not update
- Anonymous1 year ago
Hello Alexander_Faber ,
Thank you for reaching out to the Microsoft Fabric community forum. The error you're seeing indicates a timeout issue in the Fabric UI, while Azure Data Studio is functioning correctly. Also thank you nilendraFabric for your inputs
To fix this, try manually refreshing the schema by going to Warehouse > Manage Tables > Refresh Schema. If your queries are large, they might be timing out before completion, so consider breaking them into smaller parts for better performance.
If you're using Power BI, increase the Command Timeout in File > Options & Settings > Options > Query Execution. Additionally, try pausing and resuming the warehouse from the Fabric UI or reconnecting the SQL Endpoint via Settings > Manage Connections > Reconnect SQL Endpoint.
Check your Fabric capacity and resource limits, as heavy workloads can cause timeouts. If the issue persists, verify the Fabric Service Health Dashboard for any outages.
I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
I can't offer any help, just wanted to share that we are experiencing the same thing since yesterday afternoon.
I have opened a ticket for that and support is still investigating the issue.
- trutz1 year agoAdvocate IV
Using parts of this code I can find also batch jobs of type Monitor on the SQL endpoint
Workaround for delays in the automatically generated schema in the SQL analytics endpoint of the Lakehouse in Fabric | by Mark Pryce-Maher | Medium
These batch jobs also list the new tables. But there are other jobs with a refresh action from the UI that turns up with an error:{'batchId': 'aaaaaaa-adb1-4a34-8786-aaaaaaaaaaaaaa-03be-4582-b90b-e90fbb204dec$2025-02-27T16:19:35.5346803Z@f725a144-300c-4e90-bbd1-b31674256bee', 'startTimeStamp': '2025-02-27T16:19:35.72', 'endTimeStamp': '2025-02-27T16:32:55.66', 'progressState': 'failure', 'errorData': {'error': {'code': 'InternalError', 'pbi.error': {'code': 'InternalError', 'parameters': {'ErrorMessage': 'The SQL query failed while running. Message=[METADATA DB] <ccon>Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</ccon>, Code=-2, State=0', 'HttpStatusCode': '500'}, 'details': []}}}, 'batchType': 'metadataRefresh'} - trutz1 year agoAdvocate IV
We're getting the same issue.
If you run the the following SQL command, new tables show up, but not in the UI, which gives us the same error, you've been showing:SELECT *FROM INFORMATION_SCHEMA.TABLESwhere table_schema = 'dbo' and TABLE_NAME - Anonymous1 year agoNot applicable
Hello Alexander_Faber ,
We understand that you're facing an issue with SQL query execution in Microsoft Fabric Warehouse and thank you for your patience and understanding. This issue is currently a known ongoing issue affecting Warehouse SQL endpoint synchronization in the West Europe region as smue_smue mentioned. Microsoft is aware of the problem, and the team is actively working on a resolution.
For more information and updates on this issue, please refer to the official Microsoft Fabric Known Issues page:
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.