Instance trouble

[Zeno-Ira]

Stuck in another world; no duty finder or any instanced content- same as 90k error phase4

[Riaku]

SE Posted this up about an hour ago...

Regarding the Instance-Related Issues (Aug. 24)
While we were able to address the previous issue wherein players were unable to access instances, we conducted another investigation and confirmed that the issue was ongoing for a number of players.

We have been able to identify the cause of the issue and have started the recovery operations. Once we have tested the fix, we plan on conducting another emergency maintenance. We will follow up once we have a better idea on the time frame of the maintenance.

We sincerely apologise for any inconvenience this may cause.

[Amyas]

Bump.
tencahr

[Diadumenos]

Server: Ragnarok
NPC: Injured Hearer
Quest: Spirithold broken

can initiate quest with NPC and get "Proceed" button. But character either locks up to where can not even log out or I get the "A system error occurred during event movement"

[Poetrice]

What was the point of a 2,5 hours downtime if the problem is still there? I am still stucked on the main questline and can't progress 'cause of duty server problems.

We are paying for a beta disguised as "early access". I really hope we get a free play time compensation after our 1 month free period. It's sad to know that some bugs exist since phase 3.

[Caraway]

This error continues to be experienced on the Adamantoise server as well.

The symptoms are the same with Duty Finder connectivity timing out.


There is no excuse for this. Please resolve this and account for the population your game has acquired.

[Malys]

Server: Balmung
NPC: Gods' Quiver Instructor
Quest: To Guard a Guardian

Cannot connect to duty finder, character becomes stuck when trying again.

[Antharas]

Instances still borked on Leviathan <_<....

[Bishok]

Server: Gilgamesh
Quest: The Company You Keep
Error: [7:40 p.m.]A system error occurred during event movement.
[7:40 p.m.]Unable to connect to Duty Finder server. Please try again later.

[Rell]

Experiencing the same issue on Lamia, gave me an error, tried again and got stuck sitting there "occupied".