v.25.7.0.4

This update delivers essential fixes and improvements on the Robility Runner.

Bug Fix 

UIA3 Desktop Automation Instance 
Previously, when an activity in UIA3-based desktop automation encountered an exception, the associated automation instance continued running in the background—even after the Runner transitioned to the “To Check” state. This issue has now been resolved with enhanced validation, ensuring the instance is properly terminated as expected.

Current Limitations

1. Resolution Settings Enforcement
The 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 take effect immediately. They will be enforced after the system is restarted.

2. Workflow Initiation Delay
When a workflow is triggered from Robility Manager while the target machine is in a logged-off or locked state, it may take up to 2 minutes for the status to update to “Run Initiated”.

Known Issue

The Runner status on the “Resources” page at Robility Manager may not update to “Provisioned” at times, even when the machine is successfully connected and provisioned in the “Deploy Robots” page. This will be addressed in the upcoming version. In the meantime, restarting the VM once should resolve the issue when it occurs.