Myself and many of the people I play with have had repeated problems with being refused from a waitlist because of a supposed "raid lockout conflict" when there is no conflict. I don't know if oQueue is grabbing information from alts or what, but it's getting increasingly frustrating.

It's often difficult enough to get groups to show up on oQueue, but it's creating even bigger problems when I can't apply to the groups that are listed for an imaginary conflict. I don't want to have to do a hard drop, delete program files, or reinstall the whole program everytime I'd like to use it... and so far, these are the only suggestions I've found online.

Unless there is a foolproof way in place for this feature to work, trust that people are smart enough to recognize their own raid lockouts and if they aren't, then that's their problem. But this feature is inhibiting oQueue's ability to create solid groups. Plus, it's damn annoying.

i have tried to reproduce this issue with no luck.

please define the steps exactly. am i locked out from last week or is it just this week's raids? etc

I've never extended any raid lockouts, so week to week shouldn't be an issue. Repeatedly, I've attempted to queue for Garrosh kills with only having previously killed up to Thok earlier in the week, let's say. It seems like unless I'm locked right up to Garrosh, so 13/14, it has the tendency to give an error. Again, not sure if it's taking my alts who are 14/14 into account or what.

There have been complaints about this on these forums dating back to April... if the error can't be reproduced and is still causing issues for people, why not just remove it?

I'd like to note it can also be a problem when people mistakenly list their flex raid as a normal subtype. User error perhaps, but it's also very frustrating.

I agree that it should be removed.

You can't be saved to flex runs, so that wouldn't be causing a lockout issue. I, too, am having trouble re-creating this problem with multiple toons across multiple lockouts.

What I meant is Fats, is that people when running a flex group use SoO10 as subtype rather than flexible. This flags it as a normal run, and so when I go to waitlist for this run I am told I have a lockout conflict.

Reported this a few times but it seems that when the programmer can't see it... it does not exist. 5 minutes ago i had this raid conflict for soo normal Garrosh only on 4 different groups. How the hell is this program usefull when it prevents you from raiding?

hold on. your saying that a group whose leader selected SOO10 Normal but typed flexible in the description is keeping you from wait listing due to your SOO Lockout?

thats not a bug. that's how it's supposed to work.

if the RL selects the wrong type, the error isn't with oQueue but with the RL

Please don't disregard because of that.

The main issue, originally posted, has nothing to do with Flex mode.

@egrey
then please explain how i can reproduce