Semantic Model has no Refresh Errors, but Report presented old data

[electrichead]

Hello,

I have my Semantic model set to refresh four times throughout the day, roughly evenly spaced to account for users around the globe.

This morning a user in China reported a change he made on 1/5/2026 was not showing up in the report and sent me a screen shot as evidence.  When I checked myself (about 5 hours later), I did see the data in the report.  I asked him to check again and when he did, the data was showing for him as well.

Any thoughts on what could cause a this?  He didn't clear his cashe or do anything special besides closing his browser and opening it again?  I was in the report yesterday, and although main graph seems the same to me (indicating the current data was available for the report) I don't have conclusive proof.  No screenshot, just my memory.

Thanks for any insights!

[tayloramy]

Hi @electrichead, 

Is it possible that the data was loaded between you getting the screen shot and confirming that the data was available? 

If the data was loaded, it is possible that the user had left the report open and not refreshed their browser so the page was displaying old data? 

Are you seeing any errors in the refresh history?

[electrichead]

Hi @tayloramy ,

It's possible the data was loaded between the time the screenshot was taken and I checked, but because there are no errors in the refresh history I don't think it's likely without some other issue being present.

I considered if they had left the report open.  They would have had to leave it open for 10 days, which is feasible.  They reported a second user, also in China, was seeing the same issue.  Still feasible, but maybe less likely they both did.  I'll ask.

No errors in refresh history.

It doesn't seem like this is common, but figured it's worth asking about in case someone else has seen this before.

[tayloramy · Accepted solution]

Hi @electrichead, 

If there's no errors in the refresh, and data is appearing as expected right now, honestly I'd chalk it up to user error/user behaviour and call it a day. Unless it happens again that is, if it becomes a continual problem then either there needs to be some user education, or there is some technical problem.