The fact that this is even possible is something that every RPA developer should be aware of as it could save them hours of frustration and confusion while they watch hopelessly as their well engineered bot works flawlessly one minute and then fails spectacularly with no explanation other than “selector not found”. This is made even harder to diagnose as checking the application selectors with the UI explorer actually “refreshes” the application back to its original selectors leaving no trace of what happened. It would intermittently and spontaneously obliterate any trace of SAP selectors from the machine and replace them all with its own disgusting invasive selectors like a sick parasite. Snagit is a sneaky piece of screen recording software which I wasn’t even aware was installed on the machine I deployed to. I tried to get the selector of some part of the ‘saplogon.exe’ application window and found a selector from ‘snagit32.exe’ in its place. My discovery is that some screen recording applications can actually change application selectors. I plan to make my own post about it shortly. Hi there, I know this was a long time ago but I have just spent the last 2 weeks struggling with an issue that sounds suspiciously similar to yours.

Snagit could not start the recording