Quote Originally Posted by Furious View Post
It isn't a bug; it's a design choice. When you lose a member (because they failed to accept queue or because they withdraw), your group is considered a new group and is placed at the back of the queue. This isn't something done "by accident".
How would this be a design choice?
In the simplified use case of the Duty Finder the observed and wanted behaviour is that when the condition holds that one player has failed to accept the queue, that then you are put in front of the queue.

Now take a look at the extended use case, namely that there is an instance to reserve. Why would you now suddenly be put back at the end of the queue? If the simplified version puts you always* in front of the queue.
*Except when you are a premade group and someone does not accept. But that special case makes sense, as you are with a premade, and you do not want one person to not end up in the instance.

This seems like a bug to me.