Garuda's aetheryte not Attuned?

[GalaxyGirl]

I've received the quest to unlock Garuda hard mode for my new character, I talk to the guy in new Gridania and I'm off to natalan in coerthas. Everything's fine, I attune to her crystal and "quest completed" pops on screen with "duty list updated". Strangely I see the quest still in my quest list with a greencheckmark. I shrug it off and head to duty finder menu. It's not there. I then see I can still interact with the aetheryte which I continued to attune to for 10 minutes. I wrote a ticket to support but that has done little. Every time I attune it does what I said earlier; quest completed, duty finder updated, etc, but I can't actually register for it due to it being missing from the list. The bugs in this game have prevented me from meeting deadlines, I was to get my relic tonight and missed out on a raid. In August the log in bugs prevented me from reaching the goal of being server first 50, and today when I fought hydra we killed it and it said duty complete but the fight kept going leaving us to have to log out and redo the fight. You say you do updates in patches to prevent bugs like these but you're not even doing that much.

[Nemico]

I have the same problem. This being my first relic I'm hunting for, I am unlocking it all as I go. Last night I beat Ifrit Hard (twice), quest updated to fight Garuda but its not listed in duty finder. It even stopped my current group from registering for the fight. I can not continue until you fix this.

Please

[Furlamseere]

Thank you GalaxyGirl for your post outlining the trouble you are having Garuda's aetheryte not Attuned,

In order for me to submit your report, I will need some more information. You can go Here and you can find templates for Windows and PS3 that represent the kind of details we need. Once you can provide such information we can move forward and resolve this issue. For now I am going to move this thread into Insufficient Information. You will not be able to reply, so once you have gathered the requested data please create a new bug report thread.