Chrome installed in our remote is auto updating and after update most of the time it is asking to enable chrome UiPath extension on browser.
So, if this pop is coming then automation stops working as we are not watching bots 24/7 even we have attended setup, scheduled on task schedular.
So , can i add to click on enable extension if it appears with parallel activity?
or any other suggestion if you have can you please provide
i have not used parallel activity yet so please guide me
You can see above image inside if we have main 2 workflows , can i use parallel here with if and to click enable extension if appears in between anywhere?
You can fix this by installing the extension using group policy. This method silently installs the extension and enables it, without requiring user confirmation.
I would recommend a permanent fix to this scenario, since this is caused by Chrome auto-updating and resetting the extension state, ask your infra/IT team to disable Chrome auto-update via Group Policy on the VM, or pin the UiPath browser extension via policy so it’s always enabled post-update. That removes the popup entirely instead of dealing it with UI automation.
To answer your question particularly, yes, you can use Parallel activity by placing your entire flow in one branch and the extension enable checker in the other branch.
Here is a another solution I found, not tested by me
Modify the Chrome Preferences File (Advanced)
Chrome stores the enabled/disabled state of extensions inside a JSON file named Preferences located within your User Profile directory. You can parse and modify this file using a script (e.g., Python or PowerShell) while Chrome is completely closed.
Yes, you can technically use a Parallel activity, but I would not recommend using it to continuously monitor the Chrome extension popup while the main workflow is running. Both branches would be interacting with the same browser, which can cause synchronization and UI conflicts.
A better approach would be to handle the extension check before starting the main process:
Open Chrome.
Use Check App State / Element Exists to check whether the “Enable UiPath Extension” popup is present.
If it appears, click Enable extension.
Add a short delay or wait for the popup to disappear.
Continue with the main workflow.
For example:
Open Browser → Check App State → If “Enable Extension” exists → Click Enable → Continue Main Workflow
Also, if this happens after every Chrome update, I would recommend checking the UiPath Chrome Extension installation/configuration and Chrome enterprise policies rather than relying only on UI automation. If this is a production unattended setup, deploying/configuring the UiPath extension through the appropriate machine/GPO policy can be more reliable.
So, in this case, I would prefer Check App State + If over a Parallel activity.
Hey @Mathkar_kunal, you shouldn’t use Parallel as the primary solution. Instead, check the extension state before starting the automation and enable it if necessary. For production, configure the UiPath Chrome Extension through Group Policy to prevent the popup from appearing altogether.
In the Chrome Group Policy settings, add the UiPath extension to the ExtensionInstallForcelist.
Enable UiPath Native Messaging using the identifier:
com.uipath.chromenativemsg_v2
Run the command to update the group policies:
gpupdate /force
Restart Chrome and verify the installation by visiting:
chrome://extensions
chrome://policy
By following these steps, you will force-install and enable the UiPath extension, configure Native Messaging, update the group policies, and verify the settings in Chrome.
Fyi, this is against the licence terms. Attended licences are meant to be attended, as in a human triggers them and is present during the execution.
Using the task scheduler to circumvent this and trigger it unattended is violating licence terms. So stop doing that. If you want to use an attended licence, trigger it manually and attend to it.
initially i thought of this but if itself extension is not added and asking to enable it then how check app state also can work? so dropped this thought
Yes, that’s a valid point. I was considering the case where the extension is already installed and only needs to be enabled. If the extension itself is not added, then Check App State wouldn’t be a reliable solution.
In that scenario, configuring/installing the extension beforehand through the machine or browser policy would be the better approach.
Yes, exactly. If the extension is not installed, Check App State won’t help because there is no extension UI element to detect. In that case, it’s better to install/configure the UiPath Chrome Extension beforehand using browser or machine policy. Parallel would only be useful for handling independent activities, not for installing the extension itself.
I have installed with group policy using power shell command - online-
&“C:\Program Files\UiPath\Studio\UiPath\SetupExtensions.exe” /chromepolicyglobal /silent
but still today asked to enable it cehck below ss-
