[Need support]: Healnium not healing on elements which are present inside iframe elements.

Hi Team,

I have taken one test case and ran it successfully for first time . later i have tried healenium by changing web elements in debug mode. the issue is healenium didnt heal that web element . some of the elements got healed and some arent . suprisingly , the elements which are not healed are inside the iframe element .To ensure this , i have tested nearly 10 xpaths (locators) which are lying inside the iframe . All of them werent healed by healenium. Also i have tested around 20 xpaths which are outside iframe element , they have been healed by healenium succesfully . i wonder if this issue is related to iframe thing. i am using the latest healenium web and backend too.

Healenium Web version

3.3.0

Healenium Backend version

3.2.3

Selenium version

4.1.1

Platform

Java

Properties file

recovery-tries = 1 score-cap = 0.5 heal-enabled = true hlm.server.url = http://localhost:7878 hlm.imitator.url = http://localhost:8000

Logs appeared during using Healenium

[main] WARN com.epam.healenium.processor.FindElementProcessor - Failed to find an element using locator By.xpath: //input[@id='sys_display.sn_customerservice_case.account']
Reason: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@id='sys_display.sn_customerservice_case.account']"}
  (Session info: chrome=104.0.5112.81)
For documentation on this error, please visit: https://selenium.dev/exceptions/#no_such_element
Build info: version: '4.1.1', revision: 'e8fcc2cecf'
System info: host: 'system12', ip: '0.0.0.0', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.4'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Command: [28db31984bfdcec7f5d1eaf543a0a332, findElement {using=xpath, value=//input[@id='sys_display.sn_customerservice_case.account']}]
Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 104.0.5112.81, chrome: {chromedriverVersion: 104.0.5112.79 (3cf3e8c8a07d..., userDataDir: C:\Users\raghunadh10...}, goog:chromeOptions: {debuggerAddress: localhost:57744}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: WINDOWS, platformName: WINDOWS, proxy: Proxy(), se:cdp: ws://localhost:57744/devtoo..., se:cdpVersion: 104.0.5112.81, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: 28db31984bfdcec7f5d1eaf543a0a332
Trying to heal...
[main] WARN com.epam.healenium.processor.HealingProcessor - New element locator have not been found. There is a lack of reference data.
[main] WARN com.epam.healenium.processor.FindElementProcessor - Failed to find an element using locator By.xpath: //input[@id='sys_display.sn_customerservice_case.account']
Reason: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@id='sys_display.sn_customerservice_case.account']"}
  (Session info: chrome=104.0.5112.81)
For documentation on this error, please visit: https://selenium.dev/exceptions/#no_such_element
Build info: version: '4.1.1', revision: 'e8fcc2cecf'
System info: host: 'system123', ip: '0.0.0.0', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.4'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Command: [28db31984bfdcec7f5d1eaf543a0a332, findElement {using=xpath, value=//input[@id='sys_display.sn_customerservice_case.account']}]
Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 104.0.5112.81, chrome: {chromedriverVersion: 104.0.5112.79 (3cf3e8c8a07d..., userDataDir: C:\Users\raghunadh10...}, goog:chromeOptions: {debuggerAddress: localhost:57744}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: WINDOWS, platformName: WINDOWS, proxy: Proxy(), se:cdp: ws://localhost:57744/devtoo..., se:cdpVersion: 104.0.5112.81, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: 28db31984bfdcec7f5d1eaf543a0a332
Trying to heal...
[main] WARN com.epam.healenium.processor.HealingProcessor - New element locator have not been found. There is a lack of reference data.
[main] WARN com.epam.healenium.processor.FindElementProcessor - Failed to find an element using locator By.xpath: //input[@id='sys_display.sn_customerservice_case.account']
Reason: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@id='sys_display.sn_customerservice_case.account']"}
  (Session info: chrome=104.0.5112.81)
For documentation on this error, please visit: https://selenium.dev/exceptions/#no_such_element
Build info: version: '4.1.1', revision: 'e8fcc2cecf'
System info: host: 'Mysystem123', ip: '0.0.0.0', os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '17.0.4'
Driver info: org.openqa.selenium.chrome.ChromeDriver
Command: [28db31984bfdcec7f5d1eaf543a0a332, findElement {using=xpath, value=//input[@id='sys_display.sn_customerservice_case.account']}]
Capabilities {acceptInsecureCerts: true, browserName: chrome, browserVersion: 104.0.5112.81, chrome: {chromedriverVersion: 104.0.5112.79 (3cf3e8c8a07d..., userDataDir: C:\Users\raghunadh10...}, goog:chromeOptions: {debuggerAddress: localhost:57744}, javascriptEnabled: true, networkConnectionEnabled: false, pageLoadStrategy: normal, platform: WINDOWS, platformName: WINDOWS, proxy: Proxy(), se:cdp: ws://localhost:57744/devtoo..., se:cdpVersion: 104.0.5112.81, setWindowRect: true, strictFileInteractability: false, timeouts: {implicit: 0, pageLoad: 300000, script: 30000}, unhandledPromptBehavior: dismiss and notify, webauthn:extension:credBlob: true, webauthn:extension:largeBlob: true, webauthn:virtualAuthenticators: true}
Session ID: 28db31984bfdcec7f5d1eaf543a0a332
Trying to heal...
[main] WARN com.epam.healenium.processor.HealingProcessor - New element locator have not been found. There is a lack of reference data.

Additional context

Thank you No response