Hi, I love using "Click at center of found image", but lately I have been noticing that the mouse gets to the right location but doesn't click.
Has anyone else seen this? Any suggestions. Since the mouse is getting to the right location, I can add a second click to increase reliability, but thought that I should ask.
Could it be that the macro is clicking too soon (e.g. before a screen element is ready)? Instead of using one action to move and click, try using one action to just move without clicking, and follow it with a pause action and then another mouse action to just click without moving.
Yes, I've seen it with some apps. Kevin's suggestion usually solves that problem.
My approach is usually a bit different from Kevin's. I move and click UNTIL the found image has disappeared. You don't really need a Pause in that case.
Thanks... what you suggest should work... but wanted to understand how an image-match could be found without the click action be ready. Seems like atomicity is missing in some of the actions in MacOS.
It’s not that the action isn’t ready. On the contrary, my suggestion was that the screen element was not quite ready to be clicked but that may well not apply in your example. Trying to explain better what I mean probably isn’t worthwhile for either of us though. 
Try @Airy’s suggestion or mine and if there is no success, let us know more.
I like this one!! It has a bit of "If at first you don't succeed, you try and try again". Some of the folks here may be old enough to appreciate this.
It's usually the application, not the OS -- you haven't said what you're using but it is often seen with web apps and Electron-based ones where an image or button changes state when you mouse over it. KM clicks faster than you or I would and the UI element doesn't achieve its "clickable" state in time.
@Nige_S found the words that escaped me: