Why do robots remain connected and continue to execute jobs even after the license has been deallocated from the admin portal?
Issue Description:
Even after deallocating the license from the admin portal to the tenant, the robots remain connected and can execute jobs.
Root Cause:
This is expected as UiPath does not force-disconnecting machines. Either remove the license from that computer manually from Orchestrator UI or shut down/reboot the computer.
Explanation
- Move to Admin portal > {Tenantname}> Licenses > Click on Edit allocation > Allocate the Production (Unattended robot) license to the specific tenant from the admin portal.
- Move to same Tenant - Orchestrator service - Tenant > License where the license is allocated
- Assign the runtime to the machine template.
- Connect the unattended robot and the process can be executed.
Behaviour
- If deallocating the license from (5 to 0) > Move to Admin portal > {Tenantname}> Licenses > Click on Edit allocation > Allocate the Production(Unattended robot) license to the specific tenant from the admin portal and remove the count. The robot is still running from the specific tenant.
- The machine template still shows the 1 runtime that was allocated as shown below
- Since the robot is still connected to the machine and has acquired the license, UiPath is not forcibly disconnecting machines. To address this, either manually remove the license from the machine template through the Orchestrator UI or shut down/reboot the robot machine.
Note: If the scenario, for example, involves 500 runtimes allocated to a specific tenant and it is decided to deallocate 250 runtimes, it's necessary to manually remove the license from the appropriate machine template or disconnect the robot. This manual intervention ensures that if a license runtime becomes unavailable, it will not be reallocated automatically.
Resolution :
Navigate to the relevant machine template and reduce the runtime count for the specific machine to ensure that the license is deallocated.