topic Re: Unattended Execution: Element Not Found and Could not identify process owning the current foregr in Product Forum

Unattended Execution: Element Not Found and Could not identify process owning the current foreground window

esaugos — Thu, 05 Oct 2023 14:41:34 GMT

Hello,

I am getting random errors as shown below while executing the process in Unattended scenario.

Element Not Found.
Could not identify process owning the current foreground window.

When the process runs in attended mode, it works fine but the issue is only with unattended mode.

I have already gone through other posts in this topic and also followed steps over there as mentioned but no luck so far.

Also would like to highlight that the VM is in Azure Platform and we are using RDP session to login the VMs for process execution. There are no security policies in the VM which can lock the screen so its permanently unlocked. Already verified through RTR latest screen capture option whenever an exception occurs and there is no issue with screen resolution as well because its same in both attended and unattended scenarios.

Blue Prism version is 6.10.5. Kindly help resolving this issue. Screenshots below.

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foreground window

expertcr — Thu, 05 Oct 2023 17:14:11 GMT

It is hard to help you without knowing what is happening on the screen. You can check the following article "BPE error "Could not identify process owning the current foreground window" when trying to focus an application" here regarding that error.

You can enable an exception to Save a Screen Capture of the moment when it fails. So you can see what is blocking the screen or why the element is not visible.

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foreground window

esaugos — Fri, 06 Oct 2023 08:36:00 GMT

Hi @Luis Lopez,

I have already checked the exception screenshot using the screen capture. The screen is not locked and GUI is also in foreground but still random exceptions like element not found and sometimes foreground errors are coming.

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foreground window

expertcr — Fri, 06 Oct 2023 15:53:32 GMT

Can you check add before looking for the element that you use, Activate Application, just to be sure the window ready.

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foreground window

esaugos — Tue, 10 Oct 2023 15:38:43 GMT

Hi @Luis Lopez,

The issue has been resolved currently by following the below URL and executing the VM commands as mentioned here. Although Regression testing is ongoing to conclude the unattended Automation Execution in Azure VMs.

Disconnecting From Remote Desktop While Running Automated Tests | TestComplete Documentation (smartbear.com)

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foregr

EThuer — Tue, 16 Sep 2025 18:45:35 GMT

And if it is the Activate Application that is throwing the exception?

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foregr

david.l.morris — Tue, 16 Sep 2025 19:27:50 GMT

@EThuer It'd be best to create a new post and describe your scenario in as much detail as you can provide.

In general though, if activate application is throwing an exception, it means either speed of execution is your problem and you need a conditional wait stage beforehand, or the element just doesn't exist that you're targeting for the activate.

Re: Unattended Execution: Element Not Found and Could not identify process owning the current foregr

RoopkiranBevara — Wed, 17 Sep 2025 05:25:38 GMT

Hi @esaugos , In Azure Environment the VM's is in idle state for very long time. So when ever you are triggering the main process/Bot kindly use Login agent to activate the VM & wait for 1 to 2 minutes to activate resource PC & trigger your main process. These type of fore ground issues will sort out.

If any scheduler is exist add a task to restart, login, Main process, logout... Definitely this issue will be resolved. Hope this will be helpful.

Reagrds,

Roopkiran.