I’m automating workflows across both Chrome and Edge browsers. The process begins by launching a web application in Edge, followed by opening another application in Chrome. Once the Chrome application is loaded, I use the Check App State activity to verify the presence of specific UI elements.
However, for Check App State to work reliably, Chrome must be in the foreground. The issue I’m facing is that Chrome doesn’t consistently come to the foreground, even though the required element is present. As a result, the activity sometimes incorrectly follows the Else path.
I’m using the Use Browser (Modern) activity with the Chromium API input mode. I’ve tried using the Activate activity inside the chrome browser scope to bring Chrome to the foreground, but it is getting failed sometimes. How to resolve this?
Hi, @mohamedalthaf To fix Chrome not coming to the foreground for Check App State, try this: Before opening Chrome, use Kill Process to close any existing Chrome instances.
Then open Chrome fresh with Use Browser (Modern) and Chromium API.
Inside the Chrome browser scope, add an Attach Window targeting the Chrome window, then use Activate inside it to bring Chrome to front.
If Activate fails sometimes, wrap it in a Retry Scope with a small delay and retry logic.
Also make sure the UiPath Chrome extension is installed and enabled properly.
Alternatively, use Use Foreground Scope around activities needing Chrome in front.
Avoid multiple Chrome profiles or background Chrome processes as they cause issues.
Increase timeouts if the page or element takes time to load.
This approach works reliably by controlling the Chrome window activation before running Check App State.
Activate is the activity should work as it’s designed for the purpose.
Try setting it’s WaitForReady property to Complete also try increasing Delay before.
I observed that when I launch chrome for the first time, it is working and activate activity is also executing correctly. I am getting issue inconsistently in upcoming attempts.In properties of use browser, I have given open only if there is no existing session. So first time it will open chrome application. But in second and next time it will not launch everytime since it’s already there. if I launch the chrome everytime, will the issue resolve?
Kill Process is not necessary, and is overused. It’s a blunt hammer approach that can cause issues.
@mohamedalthaf Chrome does not need to be in the foreground for Check App State to work, unless you’re changing the visibility setting to fully visible.
Anyway, the Activate activity will bring the Chrome window to the front.
“it is getting failed sometimes”
When? Why? Error? Are you designating a selector inside the Activate activity? You shouldn’t. Just put it in the Use Application/Browser activity and it’ll inherit the target from that scope.
I just now checked the properties of use browser and check app state. I am not using use browser activity and check app state in same workflows. Both of them are in separate workflows. Also I noted that the resize window property of use browser was not set as maximise. In the check app state, I have kept the visibility check as fully visible and wait for page load as complete. I beleive these are the issues that is not bringing the chrome to frontend. Can you confirm?
That’s why Check App State isn’t working if the browser window isn’t in the foreground. Set that back to the default. If you’re using Chromium API you don’t need the browser in the foreground.