do you have the Extension enabled in the browser??

Hi @Yotesh Kumar Mishra ,

 Here are some suggestions that you can try:

• Check if the browser extension on which you are trying to do capture action has been enabled or not1. If it is already enabled, then try changing the current package version1.
• Try unchecking all object properties except DOMXpath and pass this in: //a title=‘Remove Format’]2. If that doesn’t work, then try adding more attributes, or target the parent/child containers2.
• Try using different capture object technologies, such as Capture object with Microsoft UI Automation (COM)3. You can find more information on how to do this here.
• If none of the above methods work, then you might have to rely on JS (Browser: Run Javascript) to get the work done2. You can also raise a support ticket with AA where] for better understanding and fixing the issue.

I hope this helps you with your issue.

@Tamil Arasu10  I have checked with extensions as it seems fine along with changed the package version also but still facing the problem. When I am doing the capture by changing the different object technologies but in that particular technology DOMXpath is not appearing in the properties. So, Bot is filling but it’s not filling in the correct textbox and then when it goes for to process for the further again it started throwing the same error in the different line.

@JasonD106468 Yes it is enabled.

Hi @Yotesh Kumar Mishra ,

Can you try with some other properties InnerHTML, label,..etc in the Recorder

Scenario 1 : Do one thing, capture the object and copy paste the xPath in a notepad file. Post that manually extract the xPath of the object using inspect element inside Google chrome. Check for any changes in both the paths.

Scenario 2 : Check for window variable, there might be something which is dynamic in the title.

Do let me know your findings 

@Yotesh Kumar Mishra make sure that the scaling of your screen is at 100%. Please note that i am facing the same issue while trying to automate Oracle Flexcube. It has “virtual” windows in the same browser tab and that is causing problems for me.