Don't Know How to Debug This Error

[Roel_Van_Gils]

Since today, I get this error every x minutes. But I'm unsure which KM macro is causing this. When I sort my macros based on last use, I only see macros that I executed myself. So my question is, what is the best way to debug this?

[cfriend]

First step is to check the KM Engine log

Open the Keyboard Maestro Engine Log in the Console or BBEdit

Hey Folks, Okay, I got irritated at having to jump through hoops to open the Keyboard Maestro Engine log... The solution? A macro of course.  A Short Press of the keyboard shortcut will open the log in BBEdit (if you have it – if you don't I encourage you to install it and use the freeware version). A Long Press of the keyboard shortcut will open the log in the macOS Console.app. Either way the logs folder gets opened in the Finder in the background for quick access to the Edi…

[Nige_S]

@Roel_Van_Gils

So my question is, what is the best way to debug this?

After checking the Engine log, as @cfriend suggests, go looking in the Editor for an "Execute a Shell Script" action that includes a call to defaults -- you could even try selecting the "All macros" group and searching for "defaults read" and then "defaults write" (and hope you aren't calling it via a script file!).

[ccstone]

The absolute first thing to try when an error occurs is to switch to the Keyboard Maestro Editor using the System UI (NOT a macro), and activate this menu item:

The next thing to try is:

After that it's time to look at the Keyboard Maestro Engine Log file.

I use the macro @cfriend references above myself (since I wrote it), but some people prefer @JMichaelTX's Display Last KM Error macro.

• Display Last KM Macro Error

[cfriend]

@ccstone

and activate this menu item:

Cool! Never seen this before. Thank you.