Hi, @olifrost. I'm glad you like the macro. Thanks for the feedback.
Theoretically, yes, but not without much more complexity that I don't plan to add to this macro. Here's why: Edit a Recently Executed Macro uses data from the Keyboard Maestro Macro Stats.plist file, thanks to the JXA code shared by @ComplexPoint. However, the plist does not contain trigger information.
When you suspect a mistaken trigger, you have a few troubleshooting options:
-
Create a Smart Group and and specify something like this:
used:2m. (On a related note, you might find this macro useful: Search All Macros) -
Search the Engine.log (Help > Open Logs Folder). For that task, you might find this macro useful: Engine.log Tool