When the log says a button is clicked but your test is not behaving as you expect after that, it's frequently the case that the click is happening, just not in the location you expect. You can check this a couple of different ways.
One, you can use Debug mode to step through the test and watch where the click is actually occurring on the screen. If this is the problem, then make sure you are using object properties to click on the button rather than coordinates (which can be different on different machines).
Another way is to turn on Visualizer and look at the images there to see where the click is happening. The fix is the same as before, using objects instead of coordinates.
I actually had some time this morning to debug this further. It seem TestComplete thinks the controls are a little bit higher in the page. When I added some click actions, I could see the cursor moving and I guess clicking things though that is not where the controls actually are.
I opened a ticket with SmartBear and it seems the issue might be because of the machine resources preventing Chrome/Edge from performing the Front End stuff basically the browser is in a frozen state. I did try reducing the open applications on the running machine and it seems to have solved it. I'm just worried now that the resource requirement for our tests to work seem to be higher than before, or possibly TestComplete might be consuming more.
