Forum Discussion
Issues with Report Refresh – Semantic Model Stuck (2nd Mail)
- 3 months ago
Hi 123abc ,
The issue may be happening because the refresh is running for a long time in Power BI Service and getting cancelled, even though it works in Desktop.
you can try the following steps to address this issue:- Open Power Query (Transform Data) and identify which table/query is taking the most time
- Optimize it by removing unnecessary columns/rows and avoiding heavy joins
- Apply filters early and move transformations to the source if possible
- Reduce the overall dataset size (avoid loading full historical data)
- If the dataset is large, use incremental refresh to reduce the load
You can also refer to these docs for more details:
https://learn.microsoft.com/power-bi/connect-data/refresh-data
https://learn.microsoft.com/power-bi/connect-data/incremental-refresh-overview
I hope this helps. Please feel free to reach out if you have any further queries.
Thank You.
- 3 months ago
Thank you very mcuh for your quick response and support.❤️
I’m trying to solve this problem because if I can’t fix it, I’ll need to rebuild the entire solution. More than 100 users are using my Sales and Planning Power BI dashboards and reports, so this issue is critical.
Right now, I wake up early every morning to manually refresh all the dashboards in Power BI Desktop and then publish them again to the Power BI Service. It has become very hectic and time-consuming for me.
- 2 months ago
hank you very much. I am pleased to inform you that the issue has finally been resolved.
After further investigation, I found that the ERP production table was not refreshing properly. The refresh process was taking approximately 6 to 7 hours and eventually stopping without completing successfully.
Our Data Administrator created a separate production table specifically for BI purposes. After connecting to the new table, the issue was successfully resolved.
I would like to sincerely thank the entire Factic Team for your outstanding support, continuous follow-up, and cooperation throughout this process. Your assistance is highly appreciated.
- 2 months ago
Hi 123abc ,
Thank you for the update.
Please continue using the Microsoft Fabric Community Forum.
Best Regards,
Anusha Bnadari.
Hi 123abc ,
The issue may be happening because the refresh is running for a long time in Power BI Service and getting cancelled, even though it works in Desktop.
you can try the following steps to address this issue:
- Open Power Query (Transform Data) and identify which table/query is taking the most time
- Optimize it by removing unnecessary columns/rows and avoiding heavy joins
- Apply filters early and move transformations to the source if possible
- Reduce the overall dataset size (avoid loading full historical data)
- If the dataset is large, use incremental refresh to reduce the load
You can also refer to these docs for more details:
https://learn.microsoft.com/power-bi/connect-data/refresh-data
https://learn.microsoft.com/power-bi/connect-data/incremental-refresh-overview
I hope this helps. Please feel free to reach out if you have any further queries.
Thank You.
Thank you very mcuh v-anbandari, i will try this and will inform you. Thanks again.
- v-anbandari3 months agoCommunity Support
Hi 123abc ,
Just checking in again on your issue. Could you please confirm if the solution worked?
Please let us know if you need any further assistance.
Thank you.
- 123abc3 months agoCommunity Champion
Thank you very mcuh for your quick response and support.❤️
I’m trying to solve this problem because if I can’t fix it, I’ll need to rebuild the entire solution. More than 100 users are using my Sales and Planning Power BI dashboards and reports, so this issue is critical.
Right now, I wake up early every morning to manually refresh all the dashboards in Power BI Desktop and then publish them again to the Power BI Service. It has become very hectic and time-consuming for me.
- v-anbandari3 months agoCommunity Support
Hi 123abc,
Thank you for the update. I completely understand your concern.
Please try the optimization steps shared earlier and monitor which query is consuming the most refresh time. That should help narrow down the root cause and reduce the manual effort involved.
I hope this helps. Please feel free to reach out if you have any further queries.