v.25.5.0.26

Estimated reading: 1 minute 179 views

This update delivers essential fixes on the Robility Runner.

Bug Fixes

Runner Status Update:
In earlier versions, the Robility Runner status did not update correctly when a machine transitioned from a “Not Connected” state to a “Running” state. This caused inconsistencies on the Resources and Deploy Robots. This issue has now been fixed to ensure accurate status updates. Click here to learn more.

Limitations

1. The specified resolution settings in the Manager are applied only during auto logon option. If the system is manually unlocked via RDP, the resolution settings will not be enforced. However, it will be reflected after the system is restarted.
2. If a workflow is initiated from the Manager while the machine is in a logged-off or locked state, it may take up to 2 minutes for the status to change to “Run Initiated”.

Share this Doc

v.25.5.0.26

Or copy link

CONTENTS