Fair play violation is not shown in team match [Fixed]

This member, @gwi02, was fair play banned but FPV has not been registered in the following team match.

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

(It is correctly shown in this team match https://api.chess.com/pub/match/1247201)

That's troubling - I hope it's a very rare occurrence.

I think it might be a one off, but I agree that if that can slip through it shows a lack of consistancy in code which is very worrying. I have also put in a bug report.

Just checked all his other matches and it seems to be correct. Just that one match error

The ability to detect closed accounts is crucial in the recalculation of match results that I carry out for a couple of leagues I'm involved with. A single closed account in a match can swing the match result one way or the other, so not being able to find every instance of closed accounts (fair play) is disturbing.

As you say, might be a one off - let's hope so.

Would you post any replies from staff here please?

Will do Stephen. Assuming I get a reply.

"Assuming I get a reply" - ah yes, good luck with that!

It looks to be correct now.

I do not know if support have intervened or if it was just very slow to propagate through to that one match. So far no response from support team.

Hey Tricky_Dicky

Just got your ticket. PLs look for my response. Also I wanted to let you know we typically answer within 24 hours of submittal

Have an awesome day today!

Thanks for the response @Kayt. What we really need to understand is did development have to fix this or was the system slow to propagate this item.

I second that! It's quite important for me to be confident that the match data I'm accessing is as accurate and as up to date as possible. If not, the admins of member clubs that take part in the leagues I help run are going to lose trust in me and my fellow organisers to run them efficiently.

We readjust match scores, applying penalties for closed accounts (fair play), right up until the point when we declare a round finished and it takes only one error in a readjusted match result to award it to the wrong team. That's disastrous in any tournament we organise.

I join to the question raised by @Tricky_Dicky and supported by @stephen_33: did developers fix something or it was just the normal behavior of the system (but data were updated with a big delay)?

I do not know of anything done by the developers or support staff. This appears to be working as designed. Most of these endpoints are cached for up to a day, and only updated if something in the match itself causes a change to the data — a game ending or similar. So the note about this user's status change will be exposed at different times in different matches. The user data supplied in the match endpoint is a convenience, but not authoritative, and so the match caches are not refreshed when the user data change.

So this looks to be just a timing issue. This particular match had had no data changes so was not updated and the change of status of a player is not classed as a data change even though it was over 24 hours but will be reflected at the next update. All the other matches in which the player had involvement had been triggered for update.

Looks as though need to allow a bit longer than 24 hours to ensure you catch all FPV's

Thanks for the answer!