Process sometimes hits this type of exceptions when it tries to click certain buttons in Edge:Įxception has been thrown by the target of an invocation. Subject: Exception has been thrown by the target of an invocation Can I ask what application you are automating? This helped, but obviously impacted the speed of processing. I also experimented with a double wait stage at the beginning of actions to wait for the element, sleep for a second and then wait for it again. You could maybe use Xpath to try and specify any attributes that could disable the element. When I inspected the element using the Chrome developer tab, you could see lots of similar elements, many of them with attributes that meant they were invisible or disabled. The system we were using was quite dynamic so the different elements on the page could change state and I got the impression that the initial wait stage was finding the element and then the page was changing slightly when it came to the navigate stage and the element was no longer in a state that allowed it to be clicked.

As you say, the problem was intermittent and seemingly random.

I found that changing from Browser mode to UIA mode and using Global Clicks got round the issue with the buttons.

I had the same issue for a client and it became quite a big problem for us.

Sharex error exception has been thrown