The work an RPA does is obvious, you can watch what it does.
Your first statement is a trusism, any solution can be a dangerous band aid, if applied incorrectly. RPAs solve real problems now, really the only correct measure.
Of the RPAs I have raised, I always watched them work, they just prevent mistakes. I would suggest taking a screen recording and verbally annotating it for posterity. Furthermore, nothing says your RPA has to run open-loop, one can put in checks to ensure that it hasn't gone off the rails.
Good advice - carefully observing the process, annotating successful (& failing) processes and installing post-hoc checks seem like sound practices. Do you have other such practices to recommend? Can you say anything about what your production and testing stack look like (esp the versions that work better)?
Your first statement is a trusism, any solution can be a dangerous band aid, if applied incorrectly. RPAs solve real problems now, really the only correct measure.
Of the RPAs I have raised, I always watched them work, they just prevent mistakes. I would suggest taking a screen recording and verbally annotating it for posterity. Furthermore, nothing says your RPA has to run open-loop, one can put in checks to ensure that it hasn't gone off the rails.