Forum Discussion
Advocate IIIReport data updated time shows up although the refresh has failed!
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.
Advocate IIIThe 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.
V-lianl-msftCommunity Support
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.- schuffa
Hello V-lianl-msft , thanks for your message. The report uses data import - no direct query. The screenshots are based on a) the datasets -> settings -> refresh history screen and b) the report information you get in the "new look" experience clicking (while the report is open) on the report name in the top middle of the PowerBI Service framework. So there is not a single chararacter of code from my side behind the both information - it's all Power BI standard features. My point is that I doubt that the "Updated" information in the second screenshot is working correctly in the described constellation. From my point of view this is a bug and needs to be fixed -> please comment.
Bets regards, Andreas
