Forum Discussion
Report data updated time shows up although the refresh has failed!
Hello, I'm doubting that this new look feature https://docs.microsoft.com/en-us/power-bi/service-new-look#2-view-report-details about showing the Data updated time stamp on the report header bar is working correctly in case of failed refreshed. Concretely I had a situation where the manual refresh failed. So in my understanding NO update of the timestamp should have happned (as also the dataset was NOT finally updated). Instead the timestamp of the last "completed" updated should still have been shown (in my example here - see also screenshots below: 7.2.2020 03:20:18 - and NOT 7.1.2020 12:06:44).
-> Can you please check and fix this?
9 Replies
Hi Member123456
I am experiencing this problem also, Refresh failed (Sharepoint as source data) > 2 hours yet the timestamp suggested that data was refreshed and showed on the report as having refreshed. I would expect the datetime to show as the last time the data refreshed. We are telling users to view the refresh info at the top of their reports, which is misleading them.
I see there was a comment Microsoft are looking into this some 14 months ago. Is there an update or an idea that we can see where this fix is at please.Refresh fails when updating data from sources that use AAD OAuth
The Azure Active Directory (AAD) OAuth token, used by many different data sources, expires in approximately one hour. You can run into situations where loading data takes longer than the token expiration (more than one hour), since the Power BI service waits for up to two hours when loading data. In that situation, the data loading process can fail with a credentials error.
Data sources that use AAD OAuth include Microsoft Dynamics CRM Online, SharePoint Online (SPO), and others. If you’re connecting to such data sources, and get a credentials failure when loading data takes more than an hour, this may be the reason.
Microsoft is investigating a solution that allows the data loading process to refresh the token and continue. However, if your Dynamics CRM Online or SharePoint Online instance (or other AAD OAuth data source) is so large that it can run into the two-hour data-load threshold, you may experience a data load timeout from the Power BI service as well.
Also note that, for refresh to work properly, when connecting to a SharePoint Online data source using AAD OAuth, you must use the same account that you use to sign in to the Power BI service.
The question is not about why the prior refresh has failed. The question is why the presented time stamp in the new look is showing an incorrect date/time stamp (the one of the failed refresh, not the one of the last correctly completed one).
P.S.: Source is here an on prem MS SQL server connected via enterprise gateway.- Hi schuffa ,The refresh failed but also showed that the refresh time may be due to direct query mode. Do you use DAX to create the refresh time or M query?Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
