The way Automation Anywhere works versus other products are similar in some fashion and different in others. What makes sense in UI Path may not make sense with us.

Speaking only from the Automation Anywhere perspective, setting up a workload management queue for a single process, let alone an attended process doesn't make a lot of sense. Generally, workload queues make sense when you have a high velocity of data that arrives faster than a single bot runner can process it.

Think about something like getting yearly healthcare renewal forms from all the employees in the company. Receiving that data and placing it into a queue to process when the bot runners are available is ideal.

It is also possible there is a construct that UI Path uses that works better for their software. I have a rudimentary knowledge of their software, but I am unaware of how and why they would use queues for an attended process.