Forum Discussion
Blank page when trying to open semantic model
Hi, just looking for some advise please as to what could cause this error.
Capacity was paused over night and restarted next day but when trying to open the semantic model I just get a balnk page and after a while an error message pops up, any suggestions please?
Many thanks in advance!
Underlying Error: {}
Activity ID: b9f994c4-4e2c-40d5-a444-f2248be0f9b0
Correlation ID: facdec8d-bfaa-701c-fcf5-11b31c358cf1
Request ID: de43f06d-cc3c-4b26-0e83-f45ab3e5a946
Time: Sat May 16 2026 18:32:53 GMT+0100 (British Summer Time)
Cluster URI: https://wabi-uk-south-d-primary-redirect.analysis.windows.net/
Hi Rocks1001,
Hope you're doing well!
Try this step by step :
1. Wait and hard refresh
Give the capacity 5–10 minutes after resuming, then do a hard refresh (Ctrl + Shift + R or Ctrl + F5) to clear cached session data.
2. Clear browser cache / try incognito
Open an InPrivate/Incognito window and try accessing the semantic model fresh, this rules out stale auth tokens or cached state from before the pause.
3. Check capacity status in the Admin Portal
Go to Fabric Admin Portal → Capacity Settings and confirm the capacity shows as fully Active (not just "Resuming"). Sometimes it shows as running but workloads haven't fully initialised.
4. Reassign the workspace to the capacity
In Workspace Settings, temporarily move the workspace to a different capacity (or shared), save, then move it back to your Fabric capacity. This forces a fresh binding and often resolves stuck states.
5. Refresh the semantic model
If you can access it via the workspace list (even if the editor won't open), trigger a manual refresh from the three-dot menu. This kicks the model out of its stuck state.
6. Open via a different entry point
Instead of opening the semantic model directly, try opening a report connected to it first, or access it via the OneLake data hub. Sometimes the model loads fine from an indirect route.
Hope this helps. Don't hesitate to ask more questions if needed. Don’t forget to Accept as Solution & give kudos if this guidance worked for you. That's motivate me to keep helping.
Best regards,
Oussama (Data Consultant & Fabric's Expert)
5 Replies
- oussamahaimoud
Memorable Member
Hi Rocks1001,
Hope you're doing well!
Try this step by step :
1. Wait and hard refresh
Give the capacity 5–10 minutes after resuming, then do a hard refresh (Ctrl + Shift + R or Ctrl + F5) to clear cached session data.
2. Clear browser cache / try incognito
Open an InPrivate/Incognito window and try accessing the semantic model fresh, this rules out stale auth tokens or cached state from before the pause.
3. Check capacity status in the Admin Portal
Go to Fabric Admin Portal → Capacity Settings and confirm the capacity shows as fully Active (not just "Resuming"). Sometimes it shows as running but workloads haven't fully initialised.
4. Reassign the workspace to the capacity
In Workspace Settings, temporarily move the workspace to a different capacity (or shared), save, then move it back to your Fabric capacity. This forces a fresh binding and often resolves stuck states.
5. Refresh the semantic model
If you can access it via the workspace list (even if the editor won't open), trigger a manual refresh from the three-dot menu. This kicks the model out of its stuck state.
6. Open via a different entry point
Instead of opening the semantic model directly, try opening a report connected to it first, or access it via the OneLake data hub. Sometimes the model loads fine from an indirect route.
Hope this helps. Don't hesitate to ask more questions if needed. Don’t forget to Accept as Solution & give kudos if this guidance worked for you. That's motivate me to keep helping.
Best regards,
Oussama (Data Consultant & Fabric's Expert)
- stoic-harsh
Super User
Hey Rocks1001,
That empty Underlying Error: {} is the key clue. The backend returned no error body at all, which means capacity is still warming up, despite showing as Active. Just wait 10-15 min and reload; hard refresh if required. Nothing is broken.
Reassigning to another capacity can speed this up slightly, but most people only have one (so you can't reassign anywhere). Everything else (incognito, alternate entry points) is worth trying but noise. To avoid this next time, schedule the capacity to resume 15–20 minutes before users are expected, rather than on demand.
That said, if something else seem to help you, please do share with us all.
Hope this helps!
Best,
Harshit
Hi Rocks1001,
One thing I would check is whether this is only the semantic model editor UI failing, or whether the semantic model itself is unavailable after the capacity resume.
I would test it in this order:
1. Try opening a report that uses the same semantic model.
- If the report works, the model is probably available and the issue may be related to the semantic model editor/session.
- If the report also fails, the capacity/model backend may still not be fully ready.2. Check the workspace item list and see whether the semantic model shows a recent refresh status or any warning.
3. Open the semantic model options from the workspace list instead of opening the model directly:
- Settings
- Refresh history
- Lineage view
- Related report4. If you are a capacity admin, check the Fabric Capacity Metrics App around the exact timestamp of the error. Look for throttling, rejected operations, or unusual activity just after the capacity was resumed.
5. Also check the Fabric support / known issues page for the cluster or region, because the error body is empty:
Underlying Error: {}In my opinion, the important part is not only the blank page, but whether other artifacts using the same model are also affected. That helps separate a UI/session issue from a capacity or semantic model availability issue.
If it keeps happening, I would raise a support ticket and include:
- Activity ID
- Correlation ID
- Request ID
- Timestamp
- Cluster URI
- Capacity name/SKU
- Workspace name
- Whether reports connected to the same semantic model still workYou can also check these:
https://learn.microsoft.com/en-us/fabric/enterprise/pause-resume
https://learn.microsoft.com/en-us/fabric/enterprise/metrics-app
v-karpurapudCommunity Support
Hi Rocks1001
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to oussamahaimoud , stoic-harsh and Burakozalp for sharing helpful suggestions.
Could you let us know if the suggested solution resolved your issue? If not, please share any additional details so we can assist further.
Best regards,
Community Support Team.- v-karpurapud
Hi Rocks1001
Just checking in as we haven't received a response to our previous message. Were you able to review the information above? Let us know if you have any additional questions.
Thank You.
