Api: GetHistoricalStatsForAccount returns an UnhandledException

Created on 14 Sep 2017 · 9Comments · Source: Bungie-net/api

Unless I'm doing something wrong here, GetHistoricalStatsForAccount (https://www.bungie.net/Platform/Destiny2/2/Account/4611686018429443774/Stats/?groups=1), returns:

{ 
  "ErrorCode": 3,
  "ThrottleSeconds": 0,
  "ErrorStatus": "UnhandledException",
  "Message": "We've encountered an error, please try again later.",
  "MessageData": {} 
}

Just to note, I've only had this issue since todays update.

bug investigation

Source

NullRoz007

👍8

All 9 comments

Do you have some update on this issue? There some way to us workaround it until it be fixed?
Thanks!

rentalhost on 19 Sep 2017

Are there any alternatives to lookup deleted characters' stats?

BinarMorker on 21 Sep 2017

@BinarMorker Oh, in the future could you make questions like this part of a separate issue? That way we don't derail Issues that are about other topics!

But to answer your question, unfortunately there is no options at the moment for accessing the information of deleted characters. I believe that, if you were to query for PGCRs that involved them, their info will still be returned: but I don't think querying directly for them will work. I'll have to test it at some point to make sure, but it's not intended behavior for deleted characters' data to be returned.

vthornheart-bng on 21 Sep 2017

I believe this question was relevant because this is the use I make of this
endpoint. Will this endpoint be accessible again?

On Wed, Sep 20, 2017 at 6:38 PM, Vendal Thornheart <[email protected]

wrote:

@BinarMorker https://github.com/binarmorker Oh, in the future could you
make questions like this part of a separate issue? That way we don't derail
Issues that are about other topics!

But to answer your question, unfortunately there is no options at the
moment for accessing the information of deleted characters. I believe that,
if you were to query for PGCRs that involved them, their info will still be
returned: but I don't think querying directly for them will work. I'll have
to test it at some point to make sure, but it's not intended behavior for
deleted characters' data to be returned.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Bungie-net/api/issues/104#issuecomment-331000684, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFh1qki5N0T535CmE8EKiIeK877G2ysWks5skZPjgaJpZM4PXFce
.

BinarMorker on 21 Sep 2017

👍1

Ohh, I see - I thought you were asking an unrelated question!

I do not have an ETA for a fix on the issue at this time.

vthornheart-bng on 21 Sep 2017

This is working again. Had to have happened in past 2 hours. My requests are working now.

iBotPeaches on 27 Sep 2017

❤1

Oy, yes! Sorry guys, that family emergency happened after I fixed it but before the fix was confirmed and deployed, so I didn't update here. Should be good to go.

vthornheart-bng on 6 Oct 2017

Thank you very much! Solid work here, works exactly as before :D

On Oct 5, 2017 8:03 PM, "Vendal Thornheart" notifications@github.com
wrote:

Oy, yes! Sorry guys, that family emergency happened after I fixed it but
before the fix was confirmed and deployed, so I didn't update here. Should
be good to go.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Bungie-net/api/issues/104#issuecomment-334624391, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFh1qgsgz2eisnBJbYBhGduyaPlylkxzks5spW49gaJpZM4PXFce
.