Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Have you guys encounter this situation before? I set my dataset to be auto refreshed twice a day. However, somebody told me they made updates a few days ago but not reflected on my report, I have comfirmed that he did made the update. First thing I do is checking if there's any refresh failures, there is one. However, 4 success refresh in a row after the failure one.
Then I go to the online service refreshed my dataset manually, then the report looks correct. Just wanted to know what could causing this issue? it's really frustrating that I can't really trust it anymore.
Solved! Go to Solution.
Hi,
Yes, I’ve seen this happen before. Even though the refresh history shows “Success”, Power BI can still sometimes show old data due to caching, gateway issues, or incremental refresh behavior.
Since the manual refresh fixed the issue immediately, the dataset itself was probably not fully updated during the scheduled refresh, even though it completed successfully.
A few common things to check:
I’d also recommend checking the detailed refresh history, not just the Success/Failed status, because sometimes individual tables can have issues.
Unfortunately, scheduled refreshes can occasionally behave inconsistently, so adding a “Last Refreshed” timestamp in the report helps users confirm the data is current.
Hope this helps!!
Thanks!
Hi @hansliu,
We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.
Thank you.
Thankyou, @SamInogic, @krishnakanth240 and @tayloramy for your responses.
Hi @hansliu,
We appreciate your inquiry through the Microsoft Fabric Community Forum.
We would like to inquire whether have you got the chance to check the solutions provided by @SamInogic, @krishnakanth240 and @tayloramyto resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you.
Hi @hansliu,
What are your data sources?
If the data source is a lakehouse or warehouse, you should add a metadata refresh to the end of the pipeline before the report refreshes.
Proud to be a Super User! | |
Hi @hansliu
Common causes might be source or dataflow delay, gateway or cache issues, or partition inconsistencies after a failed refresh. Since manual refresh fixed the issue, it’s likely scheduled refresh pulled stale data or skipped the affected partitions. You can check incremental refresh settings if you configured, gateway logs, and add a Last Refresh Time indicator in the report for validation
Hi,
Yes, I’ve seen this happen before. Even though the refresh history shows “Success”, Power BI can still sometimes show old data due to caching, gateway issues, or incremental refresh behavior.
Since the manual refresh fixed the issue immediately, the dataset itself was probably not fully updated during the scheduled refresh, even though it completed successfully.
A few common things to check:
I’d also recommend checking the detailed refresh history, not just the Success/Failed status, because sometimes individual tables can have issues.
Unfortunately, scheduled refreshes can occasionally behave inconsistently, so adding a “Last Refreshed” timestamp in the report helps users confirm the data is current.
Hope this helps!!
Thanks!
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 15 | |
| 10 | |
| 10 | |
| 8 | |
| 7 |
| User | Count |
|---|---|
| 41 | |
| 37 | |
| 35 | |
| 29 | |
| 20 |