Forum Discussion
Power BI Service Report not Refresh Properly
Hi JoJo_001001
Thanks for reaching out to Microsoft Fabric Community Forum.
Thanks for sharing the detailed behavior, since the dataset refresh is completing successfully, this appears to be related to caching at the report or session level in the Power BI Service.
As initial troubleshooting could you try the following:
- Open the report in an Incognito / Private browser session to rule out browser or session caching.
- Perform a sign-out and sign-in to Power BI Service and check again.
- Confirm the dataset refresh timestamp in the workspace to ensure the latest data is available.
- Try duplicating the report within the Service (instead of republishing) and verify if the duplicated report reflects updated data.
- If using an App, check whether the issue persists when accessing the report directly from the workspace.
Reference :
Data refresh in Power BI - Power BI | Microsoft Learn
How to configure Power BI report scheduled refresh - Power BI | Microsoft Learn
Troubleshoot incremental refresh and real-time data - Power BI | Microsoft Learn
Hope this helps!!
Thank You.
- JoJo_0010014 months agoNew Member
Hi,
Thanks for the suggestions. Apologies that I had to temporarily replace the report to mitigate the issue, so I was waiting for the problem to reoccur before testing the recommendations provided.
This issue is not limited to me — multiple colleagues are experiencing the same behaviour with this report. I don’t have access to Incognito / Private browsing, but given that everyone is affected, it seems unlikely to be a browser or session caching issue.
I have already tried signing out and signing back in, but this did not resolve the issue.
The dataset is scheduled to refresh daily and all refreshes have completed successfully with no errors. However, when the report is downloaded directly from the Power BI Service (from the report page) and opened in Power BI Desktop, the visuals immediately show the latest data.
Duplicated copies of the report exhibit the same issue.
Publishing the report again under a different name also results in the same behaviour.
Thanks.