External Data Refresh Failed

I have the same issue - worked fine for over 18 months and then throwing a very unhelpful error - it should IDENTIFY the specific field that is causing the problem and it should IDENTIFY which data is updated and which is stale.  Very BAD implementation to update some data and not others and leave the user wondering what is good and what is bad.

I am using @Investment.Price, .Change, .[Ticker Symbol],.[change (%)] ... etc.  All the typical fields that can be pulled in from @Investment.  Obviously something has been deprecated, this question needs to get to support for the @Investment data source. 

Thx

seems to  me, good customer service would not be to suggest your client to:   "report this issue to our related team" but for YOU to report the issue to the related team, explain and detail to the "related team" the work you have done to try to resolve, and include the client on the correspondence.  Then, if the "related team" assumes responsibility for the problem, consider the matter appropriately transferred.  Your thoughts on this?

Thank you.

You can see from their replies that they are not able/willing to address it.  Seems like they feel it is my (and your) problem.  I appreciate you chiming in.  Misery loves company.  If they drop it I guess I'll have to find an out side source for data feeds.    Thanks again.

This is a disgrace !

I just updated to last Office 365 (update January 2021) and this issue occurs: "We refreshed some of your data, but we couldn’t refresh all of it because we changed or removed it on our side. For the data we can no longer refresh, we’ve kept the most recent results."

Unable to see which fields are updated and which are not. Thanks a lot MS ! Very unprofessional.

I have a complex and large sheet with Stock Data which is now totally unreliable ???

You can see from their replies that they are not able/willing to address it.  Seems like they feel it is my (and your) problem.  I appreciate you chiming in.  Misery loves company.  If they drop it I guess I'll have to find an out side source for data feeds.    Thanks again.

I successively removed all the individual .attributes I was using, and I still got the error.  Then I successively deleted every security I was tracking, and I still got the error.  Typical MS - they create a feature and then walk away from it.  It's not like all of the attributes ever worked, or that every security could be quoted - so it's now just a little more broken than before.  I suspect that all the data I'm using is actually updating, and those things that never worked now throw an error.  For now I'm ignoring it but it's so annoying.