No, we do not have the queues set as active.
Our controller monitors the status of each work queue and will use AutomateC to start a process on the next available resource, based on a mapping lookup table we have in a custom SQL db. So if Work Queue A has data to be worked, run the process mapped to that queue in said table.
We do not have our resources in a pool as defined by Blue Prism - the pool is only created by how the controller handles the resources. We have it query the status of the machines either via SQL lookup or AutomateC call.
Theoretically, you could also have a process do the exact same thing in lieu of relying on the built-in controller to kick everything off.