Hello. I have encountered an issue and do not know hot to fix it. I’m level 60 with an ilvl of 153. I have three dungeon quests that I need to complete, one of which is in The Necrotic Wake. I didn’t want to go through the random group finder, so instead went to Specific Dungeons. However, I cannot queue for a single normal dungeon because it says my role (DPS) is unavailable and does not qualify for that dungeon. I do not tank, but even if I did, the tank option is also blocked out. It is like this on every single dungeon, which means I have no option but to go through the random group finder. This just occurred this evening, as I was able to use the Specific Dungeon option earlier today. Any ideas on how I can fix this?
It’s definitely something that they’re aware of. This support article includes a possible workaround that you can try until they get this bug fixed!
Awesome, thank you very much! I came across some posts about BFA issues like this, but hadn’t found that one. I appreciate the share!
I’m having this very same issue, I think.
I was able to queue for Necrotic Wake while questing through Bastion. And then, when I got the dungeon quest telling me to go there? I was locked out!
So I get annoyed, but it’s time to move on to Maldraxxus. Same thing happens with Plaguefall.
Apparently I can queue with a group… Sometimes.
But solo? I’m locked out of all roles. I can’t even queue for a random dungeon. And BOTH Plaguefall and Necrotic Wake aren’t even on the list of dungeons – just the other two (from Revendreth & Ardenweald) which I can’t get into, because I haven’t reached those zones yet.
My iLevel is 124
My character level is 59
This should NOT be a problem!
I’m feeling mighty Karenish right now.
I’m a 165 hunter and it wont let me Que as DPS, saying the role in unavailable.
I’m now level 60. (iLevel 148)
I just got the “Tirna Scithe: A Warning Silence” quest… And Tirna Scithe totally disappeared from my dungeon finder, just like happened twice before. (With Bastion and Maldraxxus)
( I’m level 60, and the four dungeons which AREN’T tied to the 4 covenants are apparently available now. )
I was able to get around the bug by dropping the party, queuing, then inviting the previous party members.
149 prot pal, need spires of ascension to continue my covenant campaign. Guess I will try and hit it with a random…
Was able to log out and back in and it seems to have fixed the issue…
This just started happening to me today too in the specific dungeon tab
edit: ran a random dungeon and was able to select specific dungeon again
I know the blue post said something about switching the group party leaders and others having done similar workarounds, but it’s happening and been happening for individuals for a while now.
Exiting the game and booting back up fixed the problem for me.
I agree that this is an issue. My own experience went similarly the same:
Hunter was lvl 57 in maldraxxus, got the quest for the dungeon (ok cool) and finished up maldraxxus quest chain, so I went to queue for the dungeon, plaguefall. Found it odd that Necrotic wake (bastion dungeon) wasn’t showing up on the timeline for specific dungeons, but I didn’t need that one, as I had already done that, and I needed plaguefall.
WHILE IN THE DUNGEON, I dinged lvl 58. ok cool didn’t think about it… until my net crapped out and I DC’d at the last boss… and when I returned I couldn’t loot the last boss for the quest item. I tried to queue again and found that I couldn’t… because I couldn’t queue for any randoms… and my specific dungeon finder… was locked, with two dungeons I couldn’t even queue for showing, none of the other two mentioned prior showing on the list.
Why blizzard would lock out or cap out the dungeons like this is frustrating as my only option I found that worked was to have a few friends, (already level 60) group with me and have one of them queue for the specific dungeon on normal. yes it still worked and I managed to complete the quest but it’s frustrating, nonetheless…
I can queue for random dungeons in a group, but when I select specific dungeons and check one, I get the warning “Role unavailable for some dungeons”. This only happens in a group, I can queue solo for specifics. I’ve passed around group lead and everyone else gets the same message. Level 60 paladin, ilevel 164. It’s been an issue since the xpack launch.
I saw this issue on my druid on Threads of Fate and was never able to specific-queue for dungeons either solo or as group lead with a friend. Passing lead to a friend worked normally. Also saw the issue once on this warrior at 60 (non-Threads since it was my first) but haven’t seen it since.
Now on my mage, also on Threads, I am able to solo queue for a specific dungeon. However, after a few minutes the “Leave Queue” button on the dungeon finder window grays out and hovering over it shows “Role unavailable for some dungeons”. After this happens, the queue never pops regardless of how long I wait.
Whatever is causing this needs to be tracked down and fixed. Very disruptive.
edit: Button seems to gray out for my mage at the 5-minute mark of the queue almost without fail.
I am experiencing this right now. Trying to queue as a paladin, all 3 roles are blocked out with the same message as OP when I’m in a group with my wife (Disc priest). When we are separate we can queue separately for specific dungeons… but we are playing together on purpose in a multiplayer game, so that sucks. We both need Spires to advance our Kirian campaign.
Yeah I have the issue when in a party. Solo I can queue just fine, random or specific, as soon as my brother (mage) joins my party I can only do randoms. Tried deleting my cache, interface, and WTF folders. Tried with no addons. Tried re-logging. has been happening since pre-patch. This is nuts.
I get this on my mage, which is unfortunate, because…i mean, dps is my only role.
Some details:
- Only happens when queing for specific dungeon while in a group
- I see a lock over the DPS role (some have reported a ! but i get a lock icon)
- Mage is max level
- Necrolord covenant
- Sometimes giving lead to someone else works, sometimes it does not
- Uninstalled wow entirely and tested on a fresh install with no mods or config, same problem.
7.Does not happen on my level 51 druid.