Forum Discussion
Schedule refresh issue
The Power BI dashboards were built in desktop using Import mode and contain a number of visuals.
Currently I am using Power BI Pro licence type to publish it to the web.
I've experienced issues with the dashboard not refreshing as scheduled in web:
Initially, I set the Dashboard to refresh daily at 9:30 AM. Occasionally, it didn't show the latest results when I opened the dashboard at 10 AM.
I reset the refresh time to 7:30 AM, as advised by the Power BI community, to refresh outside of working hours, as the visuals in the dashboard take separate times to refresh. It works for a while.
This morning, the dashboard didn't refresh to the latest data, even though it showed as completed at 7:43 AM. I manually refreshed the dashboard at the desktop level, and it worked.
How to ensure the schedule refresh is working and stable? Thks
Hi wleecwleec_2
The primary challenge relates to timing. Your Power BI Service dataset relies on an IT-managed model that refreshes at 6 AM, but this process may occasionally complete later than planned. As a result, when your dataset is set to refresh at 7:30 AM, it can begin before the source data is fully updated, leading to instances where the refresh completes without reflecting the latest data. The consistent stability of your 2 PM refresh further indicates that the refresh window is too close to the source update.To address this, adjust your morning refresh to 8:00 AM or 8:30 AM (UTC+8) to allow sufficient time after the source refresh, while maintaining the 2:00 PM refresh as your second daily run. This approach ensures both morning and afternoon refreshes remain within the Pro license limit of eight per day. Additionally, review your incremental refresh configuration to verify that the RangeStart and RangeEnd parameters are applied at the source level in a foldable step, and consider extending incremental refresh to additional tables to further enhance stability and performance
Regards,Microsoft Fabric Community Support Team.
10 Replies
Hi wleecwleec_2
Could you Please try below Steps:-
Tiles are cached: The schedule refreshes the dataset, not the dashboard tiles. Open the report to confirm data; on the dashboard click Refresh or Pin a live page so tiles always show latest.
-
UTC timing: The Service uses UTC. If your source updates after your schedule, the refresh completes with old data. Move the schedule after the source finishes (+30 - 60 min buffer) or use UTC in queries/relative date filters.
-
Health checks: Workspace >> Datasets >> Refresh history; ensure Gateway online and Data source credentials = OK.
-
Stability tips: Add a second daily run as a retry, and use Incremental refresh (or PPU/capacity) if the model is large/slow.
-
Hi wleecwleec_2 ,
When you look at Refresh History are there any messages about "failure"?Hi wleecwleec_2
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to rohit1991 and collinq for offering helpful suggestions.
Could you let us know if the suggested solution resolved your issue?If you still need help, please share more details so we can assist you further.
Thank you.
Hi wleecwleec_2
I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.
Thank You. Hi v-karpurapud,
The issue is still there, my data has confidential info.
Can advise if I paste the image of the data model and illustrate wht i hv done?Hi wleecwleec_2
Since there is no error message in the refresh history, I am unable to determine the issue without more details. As your data contains confidential information, could you please provide a sample dataset that accurately represents the problem but excludes any sensitive or unrelated content? Please share the sample in a usable format (not as a screenshot) so it can be reviewed directly. Additionally, including the expected outcome based on this sample will help me better understand your scenario and provide a precise solution.
How to provide sample data in the Power BI Forum - Microsoft Fabric Community.
Regards,
Microsoft Fabric Community Support Team.
No failure message on refresh history.
Based on the replied given, i have no idea what is tiles are cached - as no youtube advise on this.
Thus I tried incremental refresh. Is incremental refresh can work on data model where tables have "both" direction relationship? I followed youtube video on this but has error saying it has duplicate value but it works fine when i refresh the full load - i suspect "both" relationship cause the issue when set as incremental refresh......Hi v-karpurapud,
I have set incremental refresh for some tables while some tables are still using full load refresh. Sometimes it still fail to load to latest date.
I set the auto refresh time at UTC+8, Daily and Time is 7.30am and 2pm, it appears that 2pm is stable which load to latest date.
The source was using import mode where the source is from data model built by my company IT team which they set refresh at 6am which normally finish before 7.30am.
I am currently using power bi pro licence.Hi wleecwleec_2
The primary challenge relates to timing. Your Power BI Service dataset relies on an IT-managed model that refreshes at 6 AM, but this process may occasionally complete later than planned. As a result, when your dataset is set to refresh at 7:30 AM, it can begin before the source data is fully updated, leading to instances where the refresh completes without reflecting the latest data. The consistent stability of your 2 PM refresh further indicates that the refresh window is too close to the source update.To address this, adjust your morning refresh to 8:00 AM or 8:30 AM (UTC+8) to allow sufficient time after the source refresh, while maintaining the 2:00 PM refresh as your second daily run. This approach ensures both morning and afternoon refreshes remain within the Pro license limit of eight per day. Additionally, review your incremental refresh configuration to verify that the RangeStart and RangeEnd parameters are applied at the source level in a foldable step, and consider extending incremental refresh to additional tables to further enhance stability and performance
Regards,Microsoft Fabric Community Support Team.
