A customer has 2 attended bot floating licences and 50 users who can access the two licences
They are reporting that sometimes if one of the licences is not in use ‘floating’ it randomly attaches itself to one of the 50 users. The customer then advises they have ‘lost’ who has the licence and have to approach someone to look in Orchestrator to have a look for them.
Whist Ui path have confirmed the licences don’t work this way, my understanding of how the licences work is poor.
I’ve heard that the licences should disconnect themselves from a user when the process has finished running (flowed through the end process stage in the REFramework i’d assume) but this doesn’t happen to the customer, the licence remains with them unless they go to the robot tray and disconnect themselves. Should the licences disconnect themselves and become free until the next user activates the attended bot process we’ve built?
OR if this isn’t the case and the licence remains with the user until they disconnect, is there a way of making the licences do this either through an orchestrator setting or code to use in the process?
OR if you’ve faced this issue before, have you dealt with it a different way - e.g writing a process that outputs from orchestrator who has the licences at any given time so the customer can see?
Any advice would be really appreciated.