raid lockout conflict

Please, please, either fix it or remove it. I'm sick of trying to apply for groups that I qualify for only to find out I have a raid conflict that doesn't exist.

Instead of forcing the idea of recreating the issue (which you've been unable to do so far), why not just take the suggestion and remove the feature? Let us take care of our own lockouts please.

I'm the OP of the post Warlockjen linked and I can tell you it's still happening and it's got nothing to do with the listing being wrong. This error is still occuring for both myself and a number of fellow players -- both that I've spoken with and, as you can see, from the poster above -- so I don't understand why a change hasn't been made.

The "bug" can't be reproduced in order to be fixed, I get that. But as I said before, people can pay attention to their own lockouts or they can get removed from groups if they choose not to be aware of it. Either way, the point remains that this error is preventing people from joining groups for no reason whatsoever. It'd be great if something could be done about it.

Please don't disregard because of that.

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

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?

raid lockout conflict - can you please just remove it?

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.