v.25.4.0.3

This release includes key enhancements and bug fixes to improve the efficiency of Robility Runner.

Enhancements

Previously, the Runner license key was tied to a specific project. With this update, users can now retrieve and manage the license key at the tenant level via the Resources page.

Why this change?

This enhancement allows users to assign multiple projects to a single machine simultaneously, eliminating the need to manually remove the license key from one project before assigning it to another.

Impact on Users

• Users can now deploy robots across multiple projects without reconfiguring machines.
• This saves time and simplifies the deployment process.

Important Note

When assigning multiple projects to a machine, ensure that robots scheduled for deployment do not have overlapping execution times to avoid conflicts.

Bug Fixes

1. Runner Disconnection Issue
a. Previously, when a robot entered the “Not Connected” state in Robility Manager, the Runner remained connected, requiring manual intervention.
b. Now, this has been fixed, the Runner disconnects automatically when the robot is no longer connected.

2. License Expiry Notification
a. Users will now receive a notification alert when they try to connect with the expired license key.

Limitations

1. These features are only available for Unattended and High-Density Robots.
2. Resolution settings applied during workflow deployment are only enforced when using Auto Logon. Manually unlocking the system will not apply the resolution settings.
3. If the machine is logged off or locked, the process initiation from Robility Manager may take up to two minutes.
4. If a robot remains in the “Run Initiated” state for more than three minutes, Robility Manager will automatically change its status to “Not Connected”.