This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
I’m running into an issue in Microsoft Power BI Service when trying to export a semantic model to a .pbix file. When I click “Download this file,” the export popup appears, runs for about 10-20 seconds, then disappears and immediately reappears again. It keeps looping and eventually fails with the message:
We couldn't export to .pbix format.
Please try again later or contact support. If you contact support, please provide these details.
...
Status code 0
Service version 13.0.27703.46
Client version 2602.2.28113-train
Cluster URI https://wabi-west-europe-b-primary-redirect.analysis.windows.net/
What’s strange is that exporting smaller semantic models (under 10 MB) works without any issue. This specific model (size = 70 MB) was exporting successfully about 2–3 days ago, and no intentional structural changes were made since then. Most of our workspaces are on Premium/Fabric capacity.
Does anyone know if this could be an internal Microsoft issue? Has anyone experienced something similar recently on Fabric capacity??
Solved! Go to Solution.
Hi! The looping export dialog with status code 0 is usually caused by one of these things:
Large dataset storage format — if this is enabled on your semantic model (check the dataset settings in the workspace), PBIX export will silently fail. This is the most common culprit for exactly this kind of sudden breakage with no changes on your end.
Incremental refresh — if your model has an incremental refresh policy configured, export to PBIX is blocked by design.
Transient platform issue — since it stopped working suddenly, worth checking https://support.fabric.microsoft.com/support/ for any ongoing incidents in West Europe.
As a quick workaround while you investigate — open the report directly from Power BI Desktop via File → Open report → Browse reports from Power BI Service, then save locally. That bypasses the Service export entirely.
Hello @Catalin579,
Export to PBIX Fails for Large Semantic Models in Power BI / Fabric
I have seen similar issues where clicking “Download this file” triggers a looping export dialog and eventually fails with “We couldn’t export to .pbix format” (Status code 0). This typically happens for larger semantic models, even if smaller models export fine.
Common Reasons
Recommended Actions
Reference
Summary: Large or complex models may fail to export due to service limitations. Always check model settings and workspace permissions.
Hello @Catalin579,
Export to PBIX Fails for Large Semantic Models in Power BI / Fabric
I have seen similar issues where clicking “Download this file” triggers a looping export dialog and eventually fails with “We couldn’t export to .pbix format” (Status code 0). This typically happens for larger semantic models, even if smaller models export fine.
Common Reasons
Recommended Actions
Reference
Summary: Large or complex models may fail to export due to service limitations. Always check model settings and workspace permissions.
Hi @Catalin579 ,
Thanks for reaching out to the Microsoft fabric community forum.
I would also take a moment to thank @Olufemi7 and @Juan-Power-bi , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .
Best Regards,
Community Support Team
Hi @Catalin579 ,
Thanks for reaching out to the Microsoft fabric community forum.
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .
Best Regards,
Community Support Team
Hi! The looping export dialog with status code 0 is usually caused by one of these things:
Large dataset storage format — if this is enabled on your semantic model (check the dataset settings in the workspace), PBIX export will silently fail. This is the most common culprit for exactly this kind of sudden breakage with no changes on your end.
Incremental refresh — if your model has an incremental refresh policy configured, export to PBIX is blocked by design.
Transient platform issue — since it stopped working suddenly, worth checking https://support.fabric.microsoft.com/support/ for any ongoing incidents in West Europe.
As a quick workaround while you investigate — open the report directly from Power BI Desktop via File → Open report → Browse reports from Power BI Service, then save locally. That bypasses the Service export entirely.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 13 | |
| 11 | |
| 8 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 37 | |
| 27 | |
| 26 | |
| 23 | |
| 22 |