v.24.10.0.0

v.24.10.0.0

This release introduces improvements and resolves key issues to enhance your experience on our platform.

Bug Fixes

1. In high-density robot, when one user machine was disconnected and another was locked, the status in RobilityManager incorrectly displayed as “Not connected.” This issue has now been fixed.
2. The license expiry notification previously appeared multiple times during workflow execution; this has been resolved.
3. The robot status was not updated to “Running” when user machines were locked or logged off in high-density robot; now this has been fixed.
4. Previously, users could initiate a workflow for execution even when the runner license had expired. This issue has now been fixed.
5. When the interact key and vault key were not configured for the project, executing it in Runner would throw an exception. This has been resolved.
6. The Runner status was not being updated in Robility Manager; this issue has now been addressed.
7. Previously, when we connect the license key after updating the workflow version, it threw an exception as “Invalid key”. Now it has been fixed.

Limitations

1. Auto logon and auto unlock will support only for Unattended and high-density robot.
2. The given resolution settings will be applied through auto logon only. Manually unlocking the system using RPD won’t enforce resolution settings.
3. If workflow is initiated in manager when machine is logged off or locked, it won’t move to next status immediately.
4. If robot status stays in “Run initiated” for more than 3 minutes, then manager will automatically move to “Not connected” status.  But runner won’t show disconnected status if it is already connected.