You set a timeout on the actions using the facility if desired.
The find image facility itself does takes only a limited time, so it does not make sense for it to have a timeout. The issue of CPU usage occurs when the facility is used continuously, thus requiring a timeout at some higher level, at the action level.
Wondering if it is even possible to say watch for CPU utilisation which if goes over 100% for KM and runs longer for > 1minute then restart KM.
I use dropbox, one drive for work and I have set schedulers so it turns it on in the morning, before I leave office and at night so it doesn’t drain the laptop battery (hence cautious re battery drains).
Read my initial answer, it has not changed, and is marked as the solution to the problem.
You need to put a timeout on your Pause Until actions.
I don’t understand your macro at all though, it triggers when Cisco activates, and then performs actions only if Cisco is not running, which would never be the case when Cisco activates, so I presume something else is triggering this macro as well.
Nobody wants high CPU usage - you should never have high CPU usage with Keyboard Maestro unless you are actively asking it to do something hard. If this is “always” then the solution to this is to stop it from continously doing something hard.
You probably could, but this is a terrible idea. Why restart Keyboard Maestro just to cancel a macro which shouldn’t be running in the first place. if the macro is running when you don’t want it to be running, then resolve that using a timeout or otherwise.
Just some anecdotal remarks relative to KM and CPU over the past year.
One thing I have learned with KM is the Control/Option/Command/Escape feature which simply kills a running script. (It does not kill the KM engine. If I see KM in a high CPU state, this fixes it. I use this once or twice a month. And I guess that if I have to, I can set up a kill timer in the scripts of interest.
I believe ALL my runaway CPU issues with KM are related to image recognition issues, probably stuck in a loop. I use image recognition fairly often, probably more often than I should. In general, I do find VERY useful, and I execute many KM scripts employing image recognition many times every day.
I also am always running Activity Monitor. (see attached image).
I have 16GB of RAM and drive 3 monitors. Even with 20 apps open, the computer just purrs along @ low CPU usage. If I see the icon flaring up with a lot of proc usage, I can quickly go and figure out why. KM sometimes is the culprit, but more times than not, there is another culprit.