Results missing from team match endpoint

Yesterday was OK. Today showing rubbish

Example match https://www.chess.com/club/matches/1563907/games 

https://api.chess.com/pub/match/1563907 

Results missing from boards in API endpoint

Player andrewmoulden won as white but result as black (drawn) not in endpoint. 

"username":"andrewmoulden","stats":"https://api.chess.com/pub/player/andrewmoulden/stats","timeout_percent":0,"status":"premium","played_as_white":"win","board":"https://api.chess.com/pub/match/1563907/5"},

Not a unique situation. many matches show same issue.

Once the cache updates, this should be working again

Thanks Martin. So far at least 7 hours since the existing results have been removed. (Why did they get removed?)

Do we know when the cache update is expected?

They didn't get removed.

https://www.chess.com/clubs/forum/view/backend-updates-with-potential-api-impacts

The site is working on a major update that handles where a lot of data is pulling from and that includes some of the API endpoints.

It appears some of the data isn't pulling correctly and then the API gets that data. Staff thought they had fixed the issue and put the newer process back in place. Most endpoints update in 12 hours I think, so it depends on when that was last populated as to when it will get data from the original location.

Martin we can have a philosophical debate about what constitutes removal.

Data that was there yesterday and isn’t there today indicates removal as far as I am concerned.

I don’t have the luxury of viewing what the devs are doing at the back end with this major update.. My view is restricted to publicly available data access.

What it comes down to, in my opinion, is that major code changes were implemented without a full understanding of the impact this would have on, admittedly complex, datasets. Further it was done without adequate checking of the consequences.

I know this is not an easy task but again it leads me to the conclusion that the software changes are not fully understood by those applying them.

The change was posted in the club in advance and staff have been testing their code as well. This change (not the API but the underlying source and infrastructure) is something they absolutely know may have some impacts and that was the reason for the forum post and switching back after problems were found.

Some bugs can only be found under load and real world usage, especially in very complex and interconnected systems.

12 hour mark passed. Still showing error. I presume we now wait for a 24 hour cache update?

I wonder if their update is part of my complaint about the stats API. Hope it gets updated soon.

Stats were not one of the impacted endpoints

It hasn't been 12 hours since the feature changed source so it could be an hour more

21 hours. Still broken.

Looks to have been updated. Full check soon.

The newer method has been re-released.

As fae as I can tell the problem has been resolved.