Determining which macro is going rogue and debugging it

[ccstone]

@orsini

How can I determine which of the macros is causing this?

Hey @orsini,

A couple more things:

A) Look in the “Cancel” menu of the Keyboard Maestro Status menu in the menu bar, and see what's actually running.

B) Make sure you have a kill-all-macros macro with a keyboard shortcut you remember.

See these threads:

Hard Quit Stop Cancel the Keyboard Maestro ENGINE with KeyStroke

Hey Christian, You got bit eh? Everyone who uses Keyboard Maestro should have a keyboard-driven Kill-All-Maros Macro. I learned that the hard way long ago and have advocated it ever since. The macro has saved me a lot of trouble several times and completely saved my bacon once. -Chris Tags: @KillSwitch, @Kill_Switch, @Switch, @CancelAllMacros, @Cancel_All_Macros, @Kill_All_Macros, @KillAllMacros

Breaking from a running macro

Hey Jon, That's the Keyboard Maestro Status Menu in the menu bar. And no that is not how to break from a running macro; it's to cancel all running macros in case something is amiss. It's a very good idea to have a kill-all-maros macro: Kill All Macros.kmmacros (1.5 KB) [image] Because it can be easier to hit a keyboard shortcut than use the mouse in that fashion if you have a runaway process. You'll note inside the Status Menu there's a submenu called “Cancel” – from there you can cancel …

-Chris