We have created a robot that repeatedly performs screen operations, screen transitions, screen information acquisition, and input to a web application running on Edge.
This robot does all processing automatically, without human intervention.
We confirmed that the logic passed through to the end by step execution in debug mode, but when we actually tried to run the robot, errors occurred occasionally in the acquisition of screen information (GetValue) and key input (SendKeys).
It is not that errors occur 10 out of 10 times when executing under the same conditions, but sometimes errors occur 5 or 6 times.
I try to wait for the next screen to be created by WaitForCreate and make sure the screen information is displayed before GetValue is executed, but the error still occurs.
It seems that the error rate is particularly high when the terminal is under load.
Are there any effective measures to improve the above?
Also, I am considering the following measures.
I am considering the following measures, but I am not sure if they are correct.
・Set up TryCatch and add logic to redo processing in the event of an Exception.
・Sleep for about 3 seconds before processes that frequently generate errors.
I would like to hear if there is a more effective countermeasure.
Thank you in advance.
Please share the automation logic screenshot you have created along with error screenshot, also need to check what match rules are being set on web page and said controls.
@ShunsukeM6155 I believe there might be a misunderstanding in your usage. You shouldn’t need to use SendKeys and GetValue very often. Typically, you can trigger things with the PerformClick method and you can acquire text from a control by using the text property. If you have an example that you can post, I would be happy to take a look. A screenshot of your automation(s) and your adapter might be worth a look as well to get an idea of what we are helping you with along with a RuntimeLog.txt.
To enable logging, enable the FilePublisher in your %AppData%\Pegasystems\RuntimeConfig.xml and then change the logLevel for all categories (these are at the bottom of the file) to level 4.
Thanks for the reply.
I use a lot of keystrokes to control the application like a console screen.
We use WaitForCreate to check screen transitions.
An example flow would be as follows.
Errors may or may not occur during the process in the red box.
Sorry, it will take some time to get the logs into a form that can be posted here.
@ShunsukeM6155 I suggest that you examine your RuntimeLog. Make sure that all categories are set to Verbose and then reproduce the issue. That should give you some idea of what is happening. Are you getting a specific error message?
Thanks for the reply. Sorry for the delay in getting back to you.
The application to be operated is like a console screen, and there are no buttons, so the operation must be done by keystrokes, not clicks.
I have attached an example of the automation process.
Press Enter to move to the next screen. WaitForCreate until the next screen is displayed, then execute the next process to control the screen transition.
However, after the transition, an error occurs in the processing in the red frame, and the process often drops out.
Since the event occurred frequently with the same logic, after investigating the log and replacing the corresponding logic with another process, the error no longer occurred.
Thank you for your advice.
