Robotic Process Automation (RPA) Software Resources

automation is leading to an atrophy of human skills that may leave us more vulnerable when responding to unexpected situations or when things go wrong

This might be one of the case. This is like two side of the coin , but if you look the positive point of view of automation , it will definitely ease 50% of human task.

If you want to handle such situations you can make the bot an attended one. You can sent email of confirmation or any task or error to the development or deploying team in wake of any issues the bot faces so that they can resolve it manually if required. The bot can be designed in such a way that each taksbots is independent of the former taskbots and yet dependent on the task itself.lets say you want to generate an invoice,for the we can create 3 bots a data extraction bot, a data validation and finally a data entry bot. The extraction , validation and entry/submit bots are independent of each other but dependent on the task itself, i.e validation bot must be triggered if and only if there is a extracted data, if not human assistance must be requested by the bot

This can be done by using OCR (Optical character recognition) tools like 'Tesseract'

In the automation ideal business processes, a single-sign-on account is set for the bot to access the web application in production environment, thus eliminating the requirement to read Captcha. Otherwise, it is advised to exclude the captcha protected applications from standard automation. Designing a bot to read captcha, defeats the purpose of setting up captcha protection in the first place! :)

Captchas are used unauthorised bot activities, so using process automation on captcha enabled same as unethical hacking. If you are doing real automation then authorised bot should get special access to avoid the overhead.