The raid I was queueing for was marked as 10man SoO normal in the settings; as you can see I was clearly not saved to the boss at the time. I'm not sure what other information I can give besides the screenshots, it's basically that when I try to queue for a lot of raids I get the "raid lockout conflict" error regardless of what it's marked as. I understand if it's mislabeled it wouldn't work properly but in this particular case I don't think that's the issue.

edited for spelling

Raid Lockout Bug?

Hi, first let me just say thank you for creating oqueue. It has made gearing up my chars that are on dead servers extremely easy and I appreciate all the hard work that has gone into creating this addon.

I have noticed lately though that when I am trying to waitlist for raids I will get a "raid lockout" warning even though I have not killed the boss that I am waitlisting for. Here is a screenshot of savedinstances which uses Blizzard's raid lockout information: http://i.imgur.com/ytpglp2.jpg and then this is a screenshot of the "raid lockout" warning I received when attempting to waitlist for Malkorok: http://i.imgur.com/oJvVlmO.jpg

Is this a bug or is there a way to get around the raid lockout? I am currently using OQueue version 1.9.7a; while previous versions had the same issue I have found since upgrading to 1.9.7a that I have been unable to queue for a majority of raids that show up, even when I click "qualified" due to this issue. Any assistance with this would be much appreciated and if you need any other information just let me know and I will be more than happy to provide it.