Hi guys, We have a small problem and hope we can get some insights (We ported in the meantime 100% of the cloudscript code to azure, approx. 25000 LOC, everything fine, except this issue)
When a new user is created, right after logging in, we setup the user account from an azure function.
We perform 4 read requests concurrently, then build our internal data and then make 3 write requests concurrently (UpdateUserReadOnlyData, UpdateUserInternalData, UpdatePlayerStatistics). Nothing else is happening, but in approx. 40% of the cases we receive a concurrent edit error (sometimes as result for UpdateUserReadOnlyData, sometimes as result for UpdateUserInternalData)
The screenshot shows network capture where it clearly shows that no additional calls are performed (also not from the client) All keys in both UpdateUserData requests are unique Maybe I'm wrong, but it should be allowed to call UpdateUserReadOnlyData and UpdateUserInternalData at the same time?
All calls are made with a static single instanced PlayFabServerInstanceApi