Dont get me wrong, this bug is old and can be frustrating as all hell, especially when it costs people rewards.
But its a hard bug to find, even for players.
I collect the data for BD, I have multiple spreadsheets set up, with bright fancy colours, to check for bottom scores for days, how much we get if we improve on those scores with others yet to play, total scores, average score per player that counted, top and bottom scores etc etc.
Even with all of that data, it can be hard for me to find the score missing or if its a delay in the game updating, or anything else, but I have made it a lot easier on myself to do this.
For the Devs, they need to be able to search every little part of the code that may interact with GW, and then error check essentially, every line separately to find it. As it is a random bug, as in it so far has no set course as to what makes it appear and repeat, it takes even longer cause while they test it it may work perfectly.
It could be something simply like an error in rounding, or something harder to find like packet loss from too many connections running at once. We just dont know, and its up to the devs to find this error, while looking for every other reported bug and working on all the new features and fixing the problems with them too.
Im happy to keep reporting the bug as I find it, and the more data we have showing it happening and able to pin point it, like I can say with 100% certainty, I know exactly when it occurred for PG last GW for instance down to the battle that wasnt counted, the easier it might make it for the devs. Stopping GW until it is fixed would not help it at all. I think more GWs might make it easier to find though, but they cant run more GWs lol.