v.25.9.0.5

This update includes important bug fixes to improve stability and enhance the overall user experience.

Bug Fixes

1. In earlier versions of Runner, if a resource was in a Locked or Not Provisioned state when the Auto Update option was enabled and later if disabled, the Runner was still being updated automatically. This issue has now been addressed and following are the action items:

a. If the machine is in Locked state and the Auto Update option is disabled, the Runner will not be updated.
b. If the resource is in Not Provisioned state and the Auto Update option is enabled, the Runner will be updated as expected.

2. In previous versions of Runner, when a Stop command was triggered from Robility Manager, and the workflow did not stop within 3 minutes, the Runner automatically terminated the process. This issue has now been resolved.

Limitations

1. Resolution Settings Enforcement: Resolution settings configured in Robility Manager are applied only when using the Auto Logon option. If the system is manually unlocked via RDP, these settings will not apply immediately and will only take effect after a restart.
2. Starting from version 25.8.0.1, a parameter has been implemented to validate the license key connection. As a result, existing license keys will not work and cause connection or execution failures. Click here to learn more.
3. Workflow Initiation Delay: When a workflow is triggered from Robility Manager on a logged-off or locked machine, it may take up to 2 minutes for the status to update to “Run Initiated”.