BP and the application freeze

[IsilKutal_Kilin]

Hi all, We have a process that runs from control room in a virtual machine. The problem occurs at a stage where a new small window opens up in the front. The process needs to just click on a button on that front window. It is a browser based application and we identified that second window in HTML mode. We are using focus and global mouse click to click that specific item (we identified it in accessibility mode). But in that step, both the business application and BP freeze and we could be able to manually close the explorer after a while, so that the process starts again, and then continues smoothly. The thing is that this problem occurs just one time at the beginning of the process. As the process continues, it can directly pass that step for all other cases. When we manually try to proceed, we again do not face with that freezing problem in the system anytime. So, we can not stay it is a system related problem. We also put enough wait stages, but still can not handle the problem. Do you have any possible solution about this one-time freezing problem? Sincerely, Isil

[John__Carter]

Hi Isil - could it be that your BP logic is doing something to upset the target application? The target applications will have been built for humans using the mouse and keyboard. BP can do things that a human can't and sometimes you can inadvertently do something the application is not expecting. For example, on some log in screens you use the Write stage to enter credentials, yet when you press Log In an error message appears saying 'please enter a valid user name and password'. The reason for this is usually that the application is 'listening' for keyboard entry but the Write stage doesn't use the keyboard. Look back at your logic and try to see if there's any chance something like that could be happening. The 'one time at the beginning' hints that maybe the application is still settling down when the process starts the first case.

[GautamKasukhela]

Hey Isil,     We are facing a similar issue. Did you figure out the root cause for this problem and did John's approach work?   Regards, Gautam.

[Denis__Dennehy]

What you are describing is a model dialog that is blocking the messaging between Blue Prism and the app.  So Blue Prism clicks a button and is waiting for that function to complete but never gets a response because the model pop up prevents it.  If you manually closed the pop up Blue Prism would become responsive again.   This model dialog issue is described in the Java integration guide but it can occur on other application types also, as you are seeing.  There are a couple of solutions: 1. Use a Global Mouse Click instead of a window click or press action.  The Global click does not wait for a response so the model dialog issue does not occur.  2. The latest versions of Blue Prism have an application modeller timeout feature, so if an unexpected model dialog occurs Blue Prism will timeout rather than waiting forever.

[SyedRaza]

Hi, Have you tried to Activate and then use Global Mouse Click, make sure you give little between these stages. Also make sure you are using conditional wait stage for that window to appear before Activate and Global Mouse Click button. Thanks and Regards, Syed Raza

[SohanaKamat]

Hello, I am facing a similar issue in a web based application (not based on Java). The wierd part is this issue does not occur every time the bot is run on the VDI. It may occur after 50 cases or sometimes even in the first case. I have tried both modes of spying AA as well as HTML, but the response was same. Even the effort of attaching and activation before the click was futile. And it is only for this particular web application we are facing the issue, the other we application in the same process are fully responsive. But when the application as well as BP freezes we have no choice but to reboot the VDI. Is there any other approach rather than Global Mouse Click via coordinates? Kindly advise me on the same.