Currently, UpdatePlayerStatisticsResult is empty upon an UpdatePlayerStatistic request successfully returning, making it impossible to find out who the request was actually called for when calling from the Server API where you can have any number of pending UpdatePlayerStatistic requests for different players.
Due to the fact that we cannot make a second UpdatePlayerStatistic request for a player until the first has returned, reacting to the response by sending the next set of Statistics is very problematic.
Adding the PlayFabId of the player the request was called on to the Result would allow us to solve this issue very easily by simply reacting to the result instead of constantly having to try push the request until it succeeds.