Title: Auto Rec and Troubleshooting.

Q. How do you make image-based automation scenarios made by Auto Rec more stable? Is there a quick guide to fix the automation scenarios when they fail?

A. STU’s Auto Rec feature is very convenient when you need to build a quick automation scenario or when you want to build a foundation of your more complex automation scenarios without spending many resources. Auto Rec is designed to generates image-based automation scenarios where the bot will depend on images on screen or graphic user interface. While this feature provides amazing benefits like the speed of scenario development, there are some shortcomings. The scenario will have to be maintained every time graphic user interface changes. Below graphics show some tips as to where to start when image-base automation scenarios fail.

Windows operating system is a tricky system that it is no necessarily true foremost screen means it is active. You should use, Select Windows and/or Window Op to make sure the target application has the focus of the Windows OS.
Windows operating system is a slow operating system. Especially, when it is starting applications such as Excel or Adobe Acrobat Reader. The seemingly ready application on the screens are often deceiving as the application is designed to hide the fact that the preparation process in the background to receive operations. In this case, use various delays and use of various Verification operations are recommended.
Application names and titles are often used by ARGOS Low-code operations. The problem is they are often dynamic. One example is MS Office files – “sample_file.xlsx – EXCEL” can dynamically change to “sample_file.xlsx Saved” which confuses and breaks down your bot. For this type of problem, use of wildcard (*) is recommended. Just pick what is more consistent and unique over time and replace everything else with asterisk
Image-base bot relies on GUI, this includes the size and resolution/settings of the computer screen. Please make sure that the screen settings of the target environment are consistent from ones of the development environment.
Simple things make bot fail, too. Check your time-outs before you deploy your bots. Default is 120 seconds. Please give your automation scenario sufficient time to bring the process to completion.