v.26.10.0.24

This release includes the following enhancements and bug fixes.

Enhancements

1. Dynamic Troubleshoot

Enhanced the functionality to transmit the Exception Details PDF and Runner Logs ZIP as separate files through Admin Console. This enables independent storage and access in Robility Manager, improving troubleshooting efficiency while preserving existing exception metadata, notifications, and functionality.

2. Runner Log and Screenshot Storage

Improved log and screenshot storage across Azure Cloud, Google Cloud, and Database providers to ensure reliable file storage, retrieval, and downloads from AutomationOps, with enhanced validation and error handling.

Bug Fixes

1. Fixed a UI alignment issue where workflow version numbers overlapped with workflow names, improving readability.

2. Fixed an issue that caused duplicate solution names and version information to appear in the Request Received and Moved to To Check pop-up notifications.

Important

Existing Runner versions will continue to function without affecting workflow execution, and no action is required unless you need to use the Admin Console or Troubleshooting features.

To use these features, upgrade Runner to the latest version and complete the following steps:
a. Upgrade to the latest Runner version.
b. Copy the latest license key from Robility Manager.
c. Connect Runner using the updated license key.

Once these prerequisites are completed, Robility Manager can securely communicate with and manage the connected Runner machine through the Admin Console.

For more information, refer to the Admin Console documentation and Runner Diagnostics documentation.

Limitations

1. The Restart and Shutdown functionalities currently display status messages when the respective commands are initiated from Robility Manager rather than upon successful completion. For more information, refer to the Admin Console documentation.
2. When a workflow is triggered from Robility Manager on a logged-off or locked machine, it may take up to 2 minutes for the workflow status to update to “Run Initiated.”
3. Starting from version 25.8.0.1, a parameter was introduced to validate the license key connection. Existing license keys may no longer work, potentially causing connection or execution failures. Refer to the relevant documentation for more information.
4. Resolution settings configured in Robility Manager are applied only when using the Auto Logon option. If the system is manually unlocked through RDP, the configured resolution settings will not be applied immediately and will take effect only after a restart.

Limitations for Machine Template

1. The Machine Template XML file must be downloaded from Robility Manager.
2. If it does not already exist, create the MachineTemplate folder manually inside the Runner installation directory: C:\Program Files (x86)\RobilityRunner\MachineTemplate\
3. Copy the downloaded XML file into the MachineTemplate folder.

Release Date: 31.10.2026