Chrome extension getting disabled randomly by itself

Help
#1

Hello developers,
I am running an unattended process scheduled from orchestrator. The chrome browser extension for UiPath is getting disabled randomly anytime. It may run for hours and suddenly get disable hence bot will start throwing exception. On the other hand it may run for several minutes only and suddenly gets disabled.
My version of chrome is 79.
chrome extension version is 9.0.6821.

Please support folks. Urgently seeking help.

#2

Hi
Did we try with other browsers like IE as that dies need even extension and is more reliable as well

Cheers @S_Srobot

#3

The project is already developed and in prod, any other way out to handle this?

#4

I’ve also very recently had this problem. Similar to @S_Srobot said the process has been deployed processing on Chrome only, though it doesn’t make sense to migrate to IE at this stage.

I’ve only encountered the UiPath extension disabling itself once, but it happened during the night schedule where I wasn’t at hand to immediately resolve.

This definitely needs to be looked into from UiPath side, rather than Chrome.

1 Like
#5

Hello,
I too got the same error and this is very annoying. Something definitely is wrong there.
Thanks for the feedback.

#6

Hello Team,
I am facing same issue.please guide what needs to be done

#7

The issue is annoying. Everytime i need to enable the extension. Something is definitely wrong here and this is quite annoying

#8

I’m running into this same issue. Anybody find a fix? I’m really starting to think UiPath might not be reliable enough at this time for my company to use in Production.

#9

I’m also facing this issue, from time to time the chrome extension gets disabled for no reason

#10

Here also the same problem. Extension gets disabled randomly without the reason. My guess is that kill application could have some sort of impact on the Chrome settings but not sure.

#11

Hey folks.
I have the same problem. Project was running fine for several weeks then suddenly started to collapse.
What I suspect that Kill Process for chrome kills not only the browser but the linked sub-processes as well and one of them is the UiPath extension. Something somewhere might go wrong, and after the killing, the extensions needs to be enabled again manually (not always, but again sometimes). If you dont to this, even a following kill could go on error.
Definitely needs fixing from UiPath side.

1 Like
#12

Hi!
We are investigating de same problem.
In out case, we create a virtual machine with UiPath extension in Chrome and in Edge only to track the changes. We don’t execute any process in that machine and the extension still get desactivated randomly.
Our IT team thinks is a automated updates from browsers. Is there any that is investigating in this way?
Thank you in advance.

#14

One possible solution, if the machine has access to internet, is to install the Chrome extension with policy.
Starting with Studio 20.10, it should be automatically installed through policy if the conditions are met: internet access, admin rights, an enterprise licence of Studio.
For older versions of Studio or a community licence, the SetupExtensions tool can be used: About the SetupExtensions Tool

As for the cause of this issue, this needs careful investigation. Chrome can be launched with the command line flags --enable-logging --v=1 and it will collect logs in a file %LocalAppData%\Google\Chrome\User Data\chrome_debug.log
More info here: Chrome Browser debug logs - Google Chrome Enterprise Help
These command line flags can be passed in a workflow if Chrome is started with the Open Application or the Start Process activity.
It could be useful if the issue reproduces quickly. If it’s overnight then the logs could get very large.

Logs might reveal why the Chrome choses to disable the extention.

1 Like