Unable to complete a quest related to a duty

[superlazyperson]

Seems like after the latest patch (2.05 I believe), quests with a duty can't be completed and proceeded anymore.

Experienced this with The Lord Of Inferno (Lvl 20 main quest) and The Threat of Superiority (Lvl 15 Thaumaturge quest).

On both times I have completed the duty, but it doesn't proceed to the next step and still wants me to repeat that duty.

[descendant]

same here with me, I can't complete my quest doing it the bard way

[ShadowApocalypse]

Not just you tried on multiple quests and to no avil

[MissE]

They are going to perform an emergency maintenance on instance worlds in the Japanese data center. I'm guessing it's related to this problem.

Not sure about NA/EU though.

[Nadezhda]

Time 8:54AM EST
System: PC Win7
Frequency: Always
World: Anima
Character Name: Nadezhda Thelona
Class/Level: 21 Archer

NPC Name: Painted Mesa

Party Status: Solo
In-game Time: Any
Steps:
1. Commence battle for into a copper hell
2. Complete duty
3. Journal entry stays the same, no progression of quest, repeat over and over

[ShadowApocalypse]

yeah sounds like it woot

[Baldur]

I am experiencing this problem myself. For me, it's with the Notorious Biggs quest. I am able to enter the instance by speaking to Y'shtola (spelling?), complete the battle and get the Duty Complete notification. But, after the cutscene that followed the duty, the quest itself will not update. Y'shtola is still there, waiting for me to commence the duty. I tried the battle twice to no avail.

[ninthfantasy]

I'm having the same problem.

Time 2:04PM (BST/GMT +1)
System: PC Win7 64bit
Frequency: Always
World: Chocobo
Character Name: Noele Light
Class/Level: Gladiator/15

NPC Name: Owyne

Party Status: Solo
In-game Time: Any
Steps:
1. Commence story quest 'Duty, Honor, Country'
2. Complete duty
3. Journal entry stays the same, no progression of quest, repeat over and over

Update: Just tried it there (3:56PM (BST/GM+1) and managed to finish the quest and progress. Seems to be fixed for me.

[Nema]

same issue

[Nema]

problem fixed as of 10:10 AM EST at least for me anyway