Hello All!
After upgrading to 24.10.8, we started getting the error: Cannot bring the target application in the foreground. The action was blocked by the current foreground window ‘’ from the process ‘.’
It does not occur as attended. Only unattended.
We recently upgraded to 24.10.10, and it is still occurring. The issue occurs in many of our automations, but not all of them, and it happens randomly throughout the automation. It doesn’t always happen in the same place.
Is there something we can do to help mitigate this error? Maybe a property value?
Here is an example. The robot entered the credentials, and the next step is to click Login. However, we get the error described above. This does not always occur at login. It is random.
Hey @PWilliams have you tried to use activate window then after use the click or type into or any ui activities.
or if you are not able to bring the target application not able to open/Launch the application you can use Start process activity.
or try to enable this option in the use application/browser activity.
Hey @PWilliams if you having problem with type into or click . have you try with simulate or send window message . enable the retry option also check .
as your condition im expecting following error you have not done on your robot machine
Screen lock / auto lock on windows (if yes correct them){robot should be install as service mode to run as unattended }
no any correction interrupt to the system (may restart the robot server will clear it )
If the above both are ok then the error should be below 2
selectors used in your automation are correctly configured and not relying on images or anchors that may change
if its not working do this and try
change the "Login to Console as Yes " form your orchestrator for specific robot
