[Bug] Scarlet event state not updating

#1 - Aug. 25, 2013, 7:59 a.m.
Blizzard Post

Hey!

In order to save myself for being ingame all the time for completing the 13 maps achievement, I’ve written a program that uses the Scarlet events from the API to see which map is being invaded. However, on my server (Gandara), there was a bug with one of those events, which resulted into two maps being invaded at the same time (according to the API): Bloodtide Coast and Mount Maelstrom (see the screenshot).

I decided to look into the JSON, because I was not sure if this was a failure on my end. However:

{"world_id":2003,"map_id":39,"event_id":"FE5F6233-DAD6-4C63-921D-F132DFCF3397","state":"Active"},
{"world_id":2003,"map_id":73,"event_id":"11442531-6B20-411F-B0A6-D2A2C31DD668","state":"Active"},

Those two lines are from the Scarlet events from Mount Maelstrom (map_id=39) and Bloodtide Coast (map_id=73). According to one of my guild mates, Bloodtide Coast was active just before Mount Maelstrom. So I guess the server failed to update the event state? I haven’t checked the other servers though.
For reference, Mount Maelstrom was being invaded at 16:00-16:45 CEST.

And just as I was typing this, the API updated with Mount Maelstrom as failed, but Bloodtide Coast is still listed as active.

#10 - Aug. 27, 2013, 12:27 p.m.
Blizzard Post

Thank you all for reporting this problem as well as noting that it is EU-centric. I’ll be looking into it.

#11 - Aug. 28, 2013, 11:17 a.m.
Blizzard Post

We have located a part of the API system which is vulnerable to missing event updates from EU during high load periods. There was a combination of factors that caused this to be particularly bad yesterday. I have a plan to fix this problem and will as soon as I can.

#14 - Sept. 10, 2013, 10:23 a.m.
Blizzard Post

The fix is prepared. My goal is to be able to release updates and fixes with reasonably fast turn-around. But due to some process changes we are implementing internally, I need to get some infrastructure setup first before I am able to get this released. I expect updates going forward will be roughly on a two-week cadence, similar to our content releases.