Open ykslebutv opened 6 years ago
Can I quickly call "first" on recognizing the insane irony of mayhem working as designed? 😆
Yeah, if you get a chance, send over a user that you're seeing this happen on and we can take a look!
I've not been able to repro this yet. If you're seeing specific PGCRs experiencing this issue, hit me up with a PGCR ID
Just to note, we are definitely seeing Mayhem activities coming down as an improper activity mode ("AllPvP") and are investigating that further. I don't see any evidence of unusual timeouts or hanging on our side in the logs however. If you find someone experiencing these symptoms, hit me up!
@vthornheart-bng I did some debugging and must apologize - the issue is not as dramatic as I made it sound. There's no hanging or timeouts in API responses, but some data is missing from Mayhem activity history results. Imperfect exception handling in my application made it look as if responses weren't coming in.
The actual issue is that data returned by the Destiny2.GetActivityHistory endpoint is missing team and standing values for Mayhem games.
Updated the title and the first comment.
No worries, and good info - I appreciate it! Indeed, it's stemming from a regression in the bug that was causing Mayhem to return as AllPvp before. We're hoping to have a hotfix for that, though I don't have an ETA yet. I also don't know what the fate will be of the existing PGCRs that got processed as AllPvp.
thanks for the update
No prob, and thank you for the info!
Mayhem that just started today is causing PGCR calls to hang.
I can do some curls later and provide examples, but I checked this on a couple of users - once you have played a Mayhem game, your PGCRs will not return data.
UPDATE: after some debugging, looks like the issue is that data returned by the Destiny2.GetActivityHistory endpoint is missing team and standing values for Mayhem games.