Regarding Data Center Technical Difficulties Occurring After Patch 3.5 (Jan. 27): Follow-up (Updated Mar. 1)

We would like to report the current situation regarding the issues that are occurring with the Mana, Aether, and Chaos Data Centers since Patch 3.5.



Previously, we relayed that the issue is with the system which controls queuing in the Duty Finder behaving abnormally under the stress of queue congestion. Upon continued investigation, it has newly come to light that, under certain very rare circumstances queue management ceases entirely, causing the server to crash.



However, although we have a general idea of what is causing the issue, it is difficult to pinpoint completely in a dev environment. Therefore, during the Patch 3.51 HotFixes planned on February 1, 2017 (PST), we plan to implement a further system and investigative log in order to continue careful observation and implementation of a solution.



For this reason, more time will be needed until the issue is fundamentally resolved. In order to minimize the effect on our players, with the Patch 3.51 HotFixes we will be implementing a temporary solution, updating how queue management operates by making it so that when the queuing system becomes stuck, the problematic character or party's (single request) queue is canceled, thus removing the cause of the queue being stuck and preventing the server from crashing.



Should your queue become canceled, we ask that you please try queuing again. Although chances of a queue cancellation occurring due to this update are extremely small, we nevertheless apologize for the inconvenience.



We will continue to address this issue with the highest priority, and we ask for your continued patience.



We sincerely apologize for the extreme inconvenience caused to our players.





[Update: Feb. 8, 2017 12:15 a.m. (PST)]



We have been monitoring the situation, and have found no cases of queues being canceled at this time. In addition, due to the investigative log and system we implemented with the Patch 3.51 Hotfix, we have been able to confirm the situation and general cause, and the issue is planned to be addressed in the next Patch 3.55.



[Update: Mar. 1, 2017 3:00 a.m. (PST)]



This issue has been officially addressed with the Patch 3.55a maintenance which took place on Feb. 27, 2017 6:00 p.m. to Feb. 28, 2017 12:30 a.m. (PST).

We apologize for the inconvenience this may have caused.



