OpenRPA version: 1.4.56
OpenFlow version: 1.5.7
Using app.openiap.io or self hosted openflow: self hosted
Error message: none
Screenshot or video: none
Attach a simple workflow from OpenRPA or NodeRED that reproduces the error/issue: I can’t provide it because the robot works on a corporate resource
I have a problem where the robot stops detecting the browser in any way. That is, the robot cannot find the element, cannot enter data into the input fields and cannot even close the browser (I’m not sure, but it seems that you don’t even need to install an extension in the browser to close the browser)
The essence of the robot is as follows - it tries to log into the corporate system and make a couple of simple manipulations in the interface in order to make sure that this system is available for use (in other words, system monitoring). In case of an error, a corresponding notification will be sent by email and Telegram
There are several such corporate systems, and the verification of each system is carried out in subprocesses. Each such subprocess begins with the launch of the browser and ends with its closing (regardless of the result of the process)
So, we began to notice strange behavior - the robot opened the corporate system, did not enter anything into the authorization form, did not close the tab after completing the subprocess, and launched the next subprocess. Because of this, we began to open many tabs that clog the server’s memory.
This can happen once a day (that is, during one iteration of checking, nothing happened in the browser, and at the next, everything is fine and the browser closes), or it can continue to work incorrectly.
This monitoring process runs on a single robot user (HDRobots)
To solve this problem, I tried to set a pause of 3 seconds between subprocess calls. It seemed to help, but such a case still happened once.
Could this be a problem with the Google Chrome browser extension? Or maybe this is due to the fact that the browser processes do not have time to close completely when I call a new subprocess that ends up working with the wrong instance of the browser process?