Known Issues and Workarounds

Known Issues and Workarounds

Introduction
This article provides an overview of the known issues in the current build, along with their corresponding description and planned fix dates/current workarounds. These insights are intended to assist you in overcoming potential blockers during your automation journey.
Issue Description Impacted Build Planned Fix
# Type Web Text block failure Type Web Text blocked failed when combination of iframe and type web text is used #### 2026.1.0 and 2026.1.130 Please reach out to support so that they can provide a specific DLL which will help to resolve the issue. Also this will be fixed in 2026.2
# In Leapwork 2026.1.0, SSO users may not be (in some cases only) visible in the Users tab In certain environments, SSO users may not appear in the Users tab. This typically happens due to database maintenance issues—such as index fragmentation—which can cause the query responsible for fetching existing Active Directory (AD) users to time out.
It’s important to note that SSO authentication itself is not affected. Users are still able to log in successfully via SSO. However, due to these query timeouts, existing users may not be visible in the UI.
Following an upgrade to Leapwork version 2026.1.0, some customers have reported an issue where all previously configured AD/SSO users are no longer listed, and only the default admin account remains visible.
Symptoms:
- Users can successfully authenticate via SSO
- SSO users are not displayed in the Users tab in Leapwork		 #### 2026.1.0 ## For Enterprise Edition (SQL Server)
1. Open SQL Server Management Studio (SSMS) or any SQL query editor.

2. Connect to the Asset DB.

3. Run the following SQL script:

DECLARE @EmptyTenantControllerId UNIQUEIDENTIFIER = '00000000-0000-0000-0000-000000000000';<br>WITH SourceEntityIds AS<br>(<br> SELECT aur.Id AS EntityId<br> FROM dbo.ActiveDirectoryUserRole aur<br> UNION<br> SELECT agr.Id AS EntityId<br> FROM dbo.ActiveDirectoryGroupRole agr<br> UNION<br> SELECT aus.Id AS EntityId<br> FROM dbo.ADUserShortInfo aus<br>)<br>INSERT INTO dbo.TenantMapping (Id, TenantControllerId, EntityId)<br>SELECT NEWID(), @EmptyTenantControllerId, s.EntityId<br>FROM SourceEntityIds s<br>WHERE NOT EXISTS<br>(<br> SELECT 1<br> FROM dbo.TenantMapping tm<br> WHERE tm.TenantControllerId = @EmptyTenantControllerId<br> AND tm.EntityId = s.EntityId<br>);
4. Once the script completes successfully, the update is done.

## For Platform Edition (SQLite)
### Before you start: Please make sure you have the database encryption key, as you will need it during the process.
### Steps:
01. Copy and save the encryption key somewhere safe.

02. Stop the Controller service.

03. Close Leapwork Studio if it is running.

04. Take a backup of the Assets folder from this location:C:\Program Files\Leapwork\Assets 

05. Copy the Assets folder from: C:\Program Files\Leapwork\Assets 

to another location, for example Desktop.

06. Download the attached ZIP file and extract it.

07. Run WpfApp2.exe.

08. Click Open Database File, then select LEAPWORK.DB.sqlite from the copied Desktop Assets folder, and click Open.

09. Enter the saved encryption key and click OK.

10. Right-click the TenantMapping table and select Script as SELECT.

11. In the SQL editor, replace the generated query with the script below.

Important:
Before running the script, replace Users_Sqlite_File_Path with the full path of the copied Users SQLite database file (i.e. C:\Users\SachinDevTomar\Desktop\Assets\ LEAPWORK.DB.Users.sqlite) from the Desktop location.
`ATTACH DATABASE 'Users_Sqlite_File_Path' AS usersDB;
WITH SourceEntities AS (
SELECT ADUR.Id
FROM usersDB.ActiveDirectoryUserRole ADUR
UNION
SELECT ADGR.Id
FROM usersDB.ActiveDirectoryGroupRole ADGR
UNION
SELECT ADUS.Id
FROM usersDB.ADUserShortInfo ADUS
)
INSERT INTO TenantMapping (Id, TenantControllerId, EntityId)
SELECT
lower(hex(randomblob(4)))
# Web page alignment issue on chrome after chrome webdriver update to 146 After chromedriver update to 146, previously working automation flows are failing due to web page alignment issue after the chrome browser launch #### No Leapwork version specific Currently, the only available workaround for releases >= 2025.4.0 is below:
1) Close LW Studio and navigate to studio.config as per the path below:
C:\Users{user}\AppData\Local\LEAPWORK\studio.config (on Studio machine)
In config file, you will see a flag at the very bottom of the file: "UseChromeForTesting". By default, it will be set to false. Please change the value to "true" (lower case 't' without double quotes).
2) Now go to the controller machine and stop the LW controller services:
After that in the controller machine, go to the controller config file as per the below path:
C:\Program Files\Leapwork\Controller\controller.config (on Controller machine)
In the config files, you will see a flag at the very bottom of the file: "UseChromeForTesting". By default, it will be set to false. Please change the value to "true" (lower case 't' without double quotes).
3) Once done, save the file and restart the services.
4) Launch the studio and try running the flows.
And releases < 2025.4.0 the workaround is below:
Use binary location reference by extracting the zip file https://storage.googleapis.com/chrome-for-testing-public/146.0.7680.80/win64/chrome-win64.zip and then pointing to chrome.exe.
# Automation flows failing after WMA upgrade 4.0.35.0 After upgrading to WMA 4.0.35.0, previously working automation flows are failing due to breaking changes in the release. The element capture strategy has been modified, causing existing elements to no longer be recognized. This is a result of changes in WMA and is not caused by Leapwork. #### WMA 4.0.35.0
#### (not Leapwork version specific)		 Currently, the only available workaround is to recapture the affected elements within the impacted flows to align them with the updated capture strategy introduced in version 4.0.35.0
# Leapwork Data from the Temp folder is not getting removed automatically Files located in C:\Users\<UserName>\AppData \Local\Temp are not automatically deleted according to the configured Retention Policy setting. #### V.2025.4.151 This issue has been resolved and the fix will be included in the upcoming 2026.1  release.
### Workaround:
As a temporary solution, temp files can be deleted through automation flows by using either a Command Line block (for script-based deletion) or UI blocks as part of the teardown process in a run list.
# Leapwork Studio Login issue after upgrade to 2025.3.0 After upgrading to Leapwork version 2025.3.0, some users encounter a login error when attempting to access Leapwork Studio using previously valid credentials. The error message displayed is: " Wrong user credential s". 2025.3.0 User can follow below steps as fix:
01. Open the Windows Services console (press Win + R,

type

services.msc,

and press Enter).

02. Locate the service named Leapwork Controller.

03. Right-click on the service and select Stop to halt the controller.

04. Right-click again and select Properties.

05. Navigate to the Log On tab.

06. Select This Account instead of Local System account.

07. Click Browse, then choose your system or domain account.

08. Click Locations to verify the computer or domain name.

09. Enter your 

(e.g.,

VivekSawant)

and click

Check Names

to confirm.

10. Once the correct account name appears

(e.g., DOMAIN<br>
VivekSawant), click OK.

11. Enter the account password and confirm password, then click Apply followed by OK.

12. Right-click the Leapwork Controller service again and select Start.

13. Launch Leapwork Studio and log in using your previously configured credentials.
### Recommendation
For environments using domain-based authentication, it is advisable to configure the Leapwork Controller Service to always run under a domain service account with persistent credentials. This approach ensures stability during future upgrades and avoids credential mismatch issues.
# Set by Index on Fusion Dropdowns/radio buttons won't support ‘Set by' → ‘Index’ method when
"aria-rowindex" attribute (dynamic dropdown) or
data-dyn-index attribute
(radiobuttons & static dropdown) are missing in the D365 F&O application’s code.		 2025.2.200 No fix found yet as no locator is available to rely on in the D365 F&O application.

For any clarification, contact our Priority Support.