Yes there is, but it completely invalidates the purpose of using WLM queues. The purpose of those queues is to spread a large workload dataset across multiple bot runners. If you want to keep everything in the same session, you cannot spread the workload across multiple bot runners. 

Ok supposed that it is fine to log every time when item is executed, is it the purpose of WLM to run large items in the same runner? Also can the runner be associated wuth another queue?

You can make a custom solution that processes more than 1 workload item from the queue, but again that's not how WLM was designed to work. 

Also no, WLM is not designed to work with multiple queues on a single bot runner. 

The use case for WLM is quite narrow, but for spreading the processing of a large data set across multiple bot runners, it works well. 

Ok thank you it is clear now. I misunderstood the purpose of queue. I will roll back to my first solution , processing in a loop. 

​@LnMamou ,

We have a similar use case. We added logic to our bots to check if the browser is running and in a specific web page. If it is, then the bot simply processes the next WLM work item. If not, then the bot logs in to the application. The bot does not log out of the application after it finishes, and we have our unattended devices set to never sign out. Also, we don't use the Browser Automation package. We use the Browser package. I hope this helps.
 

Hello ​@joe_zuniga   thanks for your response. I thought about using Browser package but our application interface is so old and browser package wasn’t so accurate that’s why. But using Browser automation , the session is close after bot execution end

Try browser profile path option and provide any path(or user chrome profile path), this should work if your application does not log you out automatically on browser close.

Browser Automation package will automatically close the browser after bot execution. This is to ensure resource cleanup even in case of bot failures.

Hello ​@Bot Dev  our app logs us out automatically on browser close so I cannot apply this thank you. 

By the way, I download the latest version of Browser Automation 3.3.0. I have the following error message when I select a window. Can you help on this please? also please share the release notes. 

You have to use same version across all the dependent bots.

Thank you for the support. It is ok now