The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Does anyone face this issue, the visual was working fine in Power BI service. But it posted error since the 2025-02-21. Is it an environmental issue or query issue? We haven't seen this issue before and the dashboard works very good in the service.
Solved! Go to Solution.
My issue was solved on 2025/02/24 with the help from microsoft team. As investigated, the issue is from Power BI service backend, nothing related to my DAX query used to vislualize in PBI. They have identified the cause and fixed the error. Hope this won't happen again, as I can see the visual in PBI desktop but not in PBI service, which is really difficult for user to debug.
Hi @eddieisking2000,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the community members for the issue worked. If our response addressed, please mark it as "Accept as Solution" and give 'Kudos' if you found it helpful.
Regards,
Pavan.
My issue was solved on 2025/02/24 with the help from microsoft team. As investigated, the issue is from Power BI service backend, nothing related to my DAX query used to vislualize in PBI. They have identified the cause and fixed the error. Hope this won't happen again, as I can see the visual in PBI desktop but not in PBI service, which is really difficult for user to debug.
Hi @eddieisking2000,
Thank you for reaching out in Microsoft Community Forum.
Thank you @rohit1991 for the helpful response.
As suggested by rohit1991, I hope this information was helpful. Please let me know if you have any further questions or you'd like to discuss this further. If this answers your question, please "Accept as Solution" and give it a 'Kudos' so others can find it easily.
Please continue using Microsoft community forum.
Regards,
Pavan.
This error usually pops up when the Service hits internal limits (like query complexity or memory), even if the same report works fine in Desktop.
Microsoft likely rolled out a backend fix. If it happens again, I’d suggest:
Breaking down complex visuals or using simpler DAX if possible
Publishing a minimal version to isolate the issue
Checking your workspace’s capacity settings
Most of the time, it’s a temporary Service-side glitch.