I have an automation that interacts with chrome. On the VM, the automation opens chrome, but does not recognize anything on the webpage and cannot interact with it. The first step is a check app state. When watching it, the page shows up that it should identify, but it does not recognize it. Past that, it does not recognize anything else in chrome and ends up giving this error: Could not find the UI element corresponding to this selector.
I have ran this same automation on other VMs and it can successfully interact with Chrome, so it’s only on this specific VM that it is causing issues. I’ve already uninstalled/ reinstalled the UiPath extension and the error is still happening.
It looks like the issue is specific to that VM, since the same automation works fine on other VMs.
You can try these checks:
Make sure the UiPath Chrome extension is enabled and installed for the same Windows user running the bot.
Check that the Chrome and UiPath versions are compatible.
Try closing Chrome completely and restarting the VM.
Reinstall/repair the UiPath Chrome extension and restart Chrome.
Check if Chrome is running with any different permissions (for example, Administrator) compared to UiPath.
Also try opening Chrome manually on the VM and test with a simple Use Application/Browser activity to see if UiPath can detect any element.
Since the page is visible but UiPath cannot identify any elements, I would mainly check the Chrome extension, browser version, and permissions on that VM.
since it works on the other VMs, I would compare the Chrome version between them first. Open chrome://version on the broken VM and on one that works, if this one auto updated to a newer build and the others didnt, thats probably the root cause
theres a known issue going around with Chrome 149 where the extension stops seeing elements properly, theres another thread about it here from today. If thats your case, rolling that VM back to the version the working ones are on, and pausing auto update there, should get you going
also worth checking chrome://policy on both, if this VM sits under a different GPO the extension can be installed but blocked from doing what it needs
Chrome policies can leave the extension “Enabled” in the UI while silently blocking its permissions to access page content.
So, open chrome://policy in the broken VM Chrome browser and compare the status of the policies available between the working machine and the broken VM. If you find any discrepancies, then reach out to your IT and get this fixed.
Since the same automation works on other VMs, it looks like the issue is specific to this VM.
I would first check whether the UiPath Chrome extension is enabled for the same Windows user running the bot. Also check the Chrome and UiPath versions.
You can try restarting the VM and Chrome, and test with a simple Use Application/Browser activity to see if UiPath can detect any element.
If the page is visible but UiPath still cannot find the elements, I would mainly check the Chrome extension, browser version, and permissions on that VM.