[zonk]

Well, it just happened around the same time it usually happens. This time though, there was no disconnect. The console is clear, nothing new for the past 10 hours. Here's the duty info from the devmonitor:



The bot in the above screenshot is not the party leader. He appears to be stuck in the NEXT_ENCOUNTER task and so is unable to queue. All bots are in their inn rooms so they left the duty successfully, however they did not leave as they normally would; I gathered from their chat logs that they just stood there idly for ten minutes until they were automatically kicked from the duty.

For the other 3 bots it's the same as in the above screenshot, except:
Bot 1: DUTY_ENTER task, Encounter 5 (party leader)
Bot 2: DUTY_ENTER task, Encounter 2
Bot 3: DUTY_ENTER task, Encounter 5

So all bots including the leader have the DUTY_ENTER task, except one party member who is stuck with NEXT_ENCOUNTER.

Now at least we know it's not always the disconnecting causing the issue. ..

TL;DR
It looks like it's caused by the someone being stuck in the NEXT_ENCOUNTER task. When this happens the leader doesn't seem to initiate the abandon duty vote, and all the bots just sit idly until they're automatically removed from the duty due to AFK. After they're removed the one bot still remains stuck in NEXT_ENCOUNTER and the group is unable to do anything. So they all just sit in their inn rooms forever, until I check/uncheck the stuck bot's enable box.

What could be getting that one bot stuck in the NEXT_ENCOUNTER task? I'm losing so much productivity from this that it's not even worth it for me.