BLM AF FIGHT WON BUT NO REWARD

Hi Technical Support,

Last night me and a whole party (including 3 other BLM who had same problem as me) spent 4 hours doing BLM AF Body fight and at the end of it after we won the fight, we were stuck in an instance,:mad: no CS, we ran around and not matter what we did, the quest would not complete. One by one we sadly left instance, logged dropped from PT...tried everything but we didn't get the CS or quest completed.:mad:
I really don't feel like I want to spend another 4 hours doing this fight.:(
It took so long as we had to change strategy after we noticed the adds were popping at unusual times when Blizzara was not even up.... even though we were our spells right.
My request is could you please update my quest status.
I have plenty of witnesses if required to confirm we got the win, but I suppose you have server logs anyway.... please can you give me the reward I deserve for this 4 hours.
I'm anticipating some questions I will get asked so I will provide answers in advice.

Yes I entered as BLM, I was even using some AF.
I didn't change job during fight, not that this matters.

May have to move this to the Bugs forum and provide some other information.

same thing happened to my group when i got my coat. we jsut had to elave the instance and fight it again. once you win its no big deal to do it again

Problem is whole party went after the win. Putting a PT together for AF isnt always easy! and the battle can take time to win sometimes. I looked in the bug section and another player has reported the exact same problem. I just want my quest status corrected then I would be satisfied I have received "Technical Support" if I have to go and do it again, this is not "Technical Support"

We had this glitch too...some of us were able to 're-enter' and get a cs, but we still had to re-do fight again, for one BLM. This was during the first couple days of patch release, sorry to hear it still happens :/. I hope you can get your coat/burst soon :)

Thanks. I did the fight again and got it now. I cannot think what caused it yesterday, it must be something random. SE are aware of the issue and I hope they fix it soon!