Korigus

„AH API and error 500” wysłany: 13 lat temu

The issue with EU-Galakrond should also be fixed now:
http://eu.battle.net/api/wow/auction/data/galakrond (no longer giving 500 errors)
{
"files":[
{
"url":"http://eu.battle.net/auction-data/6a60b6f02d575a8f3aa64e065f23be00/auctions.json",
"lastModified":1323915445000
}
]
}

„AH API and error 500” wysłany: 13 lat temu

Thank you very much for your updates :). They are very appreciated.

Regarding your third answer. Does this mean that when multiple files are provided, we can safely assume that a snapshop won't be split in two different files and that multiple files will only mean that they are different and complete?

Yes, each file should always be a complete snapshot. This mechanism exists just in case we allow previous snapshots to exist beyond the next data refresh. We do not have any current plans to adjust the current deletion policy, but feel free to add support for this scenario if you would like.

„AH API and error 500” wysłany: 13 lat temu

Thank you very much for your updates :). They are very appreciated.

Regarding your third answer. Does this mean that when multiple files are provided, we can safely assume that a snapshop won't be split in two different files and that multiple files will only mean that they are different and complete?

„AH API and error 500” wysłany: 13 lat temu

The previous stability updates should be finished at this point.

The major 500s were while we were making the updates for EU, however it took somewhat longer than expected.
As part of a separate investigation, there is a unrelated unique case specific to EU-Galakrond that we discovered. We'll look at getting out a possible fix for that shortly.
That .tmp file entry is invalid and should be ignored -- It should disappear during the next refresh of the data. The real reason for multiple files in that list is if there are multiple snapshots available at the same time (in which case you can pick the most recent snapshot if you only want the current one).

„AH API and error 500” wysłany: 13 lat temu

The previous stability updates should be finished at this point.

The major 500s were while we were making the updates for EU, however it took somewhat longer than expected.
As part of a separate investigation, there is a unrelated unique case specific to EU-Galakrond that we discovered. We'll look at getting out a possible fix for that shortly.
That .tmp file entry is invalid and should be ignored -- It should disappear during the next refresh of the data. The real reason for multiple files in that list is if there are multiple snapshots available at the same time (in which case you can pick the most recent snapshot if you only want the current one).

„AH API and error 500” wysłany: 13 lat temu

Thank you very much. Tho, EU-Galakrond is still returning an error 500.

Good find. As it turns out, this is a completely unrelated issue that also appears to be the causing Galakrond to not appear in the realm status list:
http://eu.battle.net/api/wow/realm/status

Sorry for the inconvenience while we get that error corrected.

„AH API and error 500” wysłany: 13 lat temu

Greetings,

The current issue causing the 500 error on the /api/wow/auction/ requests should be resolved for any US/EU realms experiencing this. All auction house data dumps should be updating like normal now.

As part of this investigation, we have also planned to make a few upgrades which made lead to a brief period of where realm data may appear "temporarily unavailable". Any downtime from this should be very minimal and completed within a day or two.

„AH API and error 500” wysłany: 13 lat temu

„Auction House API is live!” wysłany: 13 lat temu

Regarding the "???" names, this is a known issue where an unknown user (to the Armory) has posted an auction. This is typically when a newly created character's data has not reached the Armory yet, so the name is unable to be displayed. Once the data is delivered to Armory, future auctions by these characters should display correctly again.