Dev Tracker

Just an update, we believe we are able to reproduce the 400 issue. It seems likely it is a secondary effect of repeatedly losing your login session. Why the session is being lost in these cases is not currently clear.

Are most of you that are experiencing the 400s also experiencing unexpected logouts?

Hello all,

We have a theory as to what is going on. It seems likely that the size of your browser's requests to our servers is bigger than the default limit we accept. In particular it seems likely that this is due to a large quantity of cookies being sent with the request. This seems consistent with peoples' descriptions of it taking a while to happen again after clearing cookies, and not happening as frequently (or at all) in incognito mode, as well as the forced logout (if some layer is dropping the login cookie due to space limits.)

To help us narrow this down -- does this ever occur when the URL does not have a www1 in it? If it happens to you please check the URL in your browser and let me know if it ever happens on a non-www1 page, because that would let us know if we are doing something wrong or if it is cookies from another source (e.g. advertisements.)

Thank you @FallenAngel , that helps us narrow things down a bit!

Hello all,

Sorry for the interruptions you are experiencing, we will start looking into this.

Can someone please provide a screenshot of what this error page looks like when you receive it?

Thanks!

Hello all,

It looks like the sheer number of searches being done via Dragon Search earlier today was impacting the availability of other search features on the site. I apologize for the interruption to the Auction House! It looks like things are better now, but we will be monitoring the situation.

This issue should now be fixed, please let us know if has improved or not.

Thanks!

Hello all,

Thank you all for your patience with this issue. We believe this has now been fixed. Please let us know if the fix is working for you or not!

We are able to reproduce this issue and are actively looking into it. Thanks for the reports everyone!

Hello all,

We believe this issue is caused by the same underlying problem that has been affecting naming dragons from their profile page and clicking the "Okay" button after exalting a dragon.

While it looks like the systemic issue causing the symptoms described in this thread may be resolved soon, we are looking into whether we can apply a workaround specifically for this issue in order to shorten the time until this problem is resolved.

Thanks for your patience while we work through this!

Hello all,

We believe we have deployed a fix for this issue. Please let us know if there is an improvement or not.

It appears the underlying issue causing this problem was the same as the one that was affecting naming unnamed dragons from their dragon profile page. We have manually worked around the issue in both of these locations while we work on a broader fix for other areas of the site behind the scenes.

Thank you for your patience everyone!

Hello all,

We are now confident we have identified the actual cause of this problem, and we are working to address it! Thank you all for your patience, I know this has been frustrating. We will provide updates as the work continues.

We have deployed a more complete change that we hope might resolve the issue for some players. You may need to refresh the dragon's profile page before trying again.

Additionally, as of a minute or two ago we have deployed a change that may fix the issue for some players. It is based on a theory about what is going wrong, so let us know if it improves anything for you!

The fix had some issues so we had to back it out, please bear with us while we work on cleaning it up a little more.

All alerts from February 24 Server Time and earlier should now have correct timestamps again. Some alerts from February 25 may still have the wrong hour/second displayed, but there shouldn't be any more glitches with alert timestamps going forward.

Thanks for your patience, everyone!

Hey everyone,

We have begun slowly filling back in the correct timestamps for alerts that were affected. The process may take several hours as there are a lot of alerts to update.

Once this process finishes, some alerts that were genuinely created today might still be out of order (e.g. they will show February 25 but the wrong hour/minute.) But all alerts older than that should be correct.

Hello all,

I apologize for the alert spam! We are in the process of cleaning up some of our internal data related to alerts, and it appears to have unintentionally updated their timestamps as a side effect. This is leading to the incorrect ordering you are seeing on your Alerts page.

We are currently evaluating our options to see if it is possible to restore the old timestamps.

@Gemmi

Thanks for the bug report, we will get this fixed!

Hi @hyphen @cloudydawn

We have confirmed there is a bug with this Which Waystone card and we will be addressing it. Thanks!

Hi @Nelsothy

Thanks for your report, it looks like this is probably a result of accidentally double tapping the button to claim the feat, so the 2nd tap gets an error message because it was already claimed from the 1st tap. We are working on making this situation smoother.

@Renaela

Don't worry, we are still working on this issue -- you haven't been missed!

@Balerion

Upon investigation it appears that our updates yesterday morning affected the 45 day refill feature unintentionally. During a period from approximately 06:00 Server Time, Jan 20 (yesterday) to 10:05 Server Time, Jan 21 (today) users that should have received a refill would have received the notification about it, but their dragons' energy was not refilled.

We have fixed it going forward, and we are currently looking into our historical data to identify the accounts that should have received the energy refill but did not. Thank you for reporting this!

These issues have been fixed. Thanks for reporting @ShadowTheEdgehog !

@DrakeNogard

Try it again now.

@DrakeNogard

Are you still getting the same error as before on trading post, or are you getting a new one?

@DrakeNogard

I apologize, you registered during a period where we were dealing with some issues as a result of a migration. I have manually fixed some of the data associated with your account. Let me know if it is working better for you now!

@IAmUniverse @HolyHavoc @RecoveryGirl

We have deployed a fix, can you let me know if it's working any better for you now?

@Storygeek

Can you try again now and let me know if it is working better?

@Theophilus

Thank you for the report. We believe we have a fix for this, but we have currently disabled Crossroads access until we can be 100% sure that no other bugs snuck in! Thank you for your patience in the mean time.

@ILoveMyBirds @CountingChocobos

Thank you for the report. We believe we have a fix for this, but we have currently disabled Crossroads access until we can be 100% sure that no other bugs snuck in! Thank you for your patience in the mean time.

@LilyDragonQueen

Thank you for the report. We believe we have a fix for this, but we have currently disabled Crossroads access until we can be 100% sure that no other bugs snuck in! Thank you for your patience in the mean time.