v.26.3.0.19

Estimated reading: 2 minutes

In this release, we have fixed the following bugs:

Bug Fixes

1. Runner Connection Across Tenants
When a user has more than one tenant and pastes a key into the Runner, then disconnects and later pastes another tenant’s key, the Runner incorrectly shows the key as “invalid” even though the previous key got disconnected.
This issue has been fixed.

2. Incorrect Status for Machine Templates
Previously, when a VM was configured with both a Machine Template and an Unattended Robot, the system incorrectly displayed the “Logged Off” status for the Machine Template after logging out of the Unattended Robot.
This issue has been fixed, and the status is now displayed correctly.

3. All Logs Displayed in Runner Page
Previously, the Runner execution page displayed all activity log levels instead of only execution output logs. This issue has been fixed.

Action Required

Note: If you continue using existing versions of Runner 26.3.0.12, they will work without affecting execution, and no action is required.

1. If the Runner was auto updated, or if you have installed the latest version, the existing automation workflow may fail. In this case, you must follow these steps:
a. Update the Designer.
b. Update the corresponding activities in your workflow.
c. Republish the workflow in the Designer.
d. Execute the workflow in the Runner.

Limitations for Runner

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 take effect only after 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.”

Released Date: 28.03.2026

Share this Doc

v.26.3.0.19

Or copy link

CONTENTS