I’m new to Keyboard Maestro, just a couple of days. Liking it so far. I am getting an error about not fidning an image and I am looking at the engine.log file to find out which action in my macro is causing it. It gives me a number 4563 and I put this in the search bar in KM but no action show u…

Welcome to the forum, @Ian-SAfc . [image] Ian-SAfc: How do I find out what action is causing the image issue? The easiest way is to use the menu command View > Go to Last Aborted Action. I believe that In theory, you should also be able to find the relevant action by selecting all macro grou…

[image] Ian-SAfc: It gives me a number 4563 and I put this in the search bar in KM but no action show up. As @kevinb says, prefix the UID with action: or act: -- do not have a space between the : and your first number: [image] Remember that only the selected Group is searched -- in the scr…

Is there any logic to why the design is such that the space has to be omitted? I presume that there is (but it shouldn’t be necessary just to, say, separate search terms :thinking:).

[image] kevinb: Is there any logic to why the design is such that the space has to be omitted? Everything immediately after the : is the qualified search term, a space outside double-quotes means "and here comes the next term". So act:<space>1234 would be "search for the Action whose ID is <n…

Right, so space characters of any kind or quantity could be searched for without being quoted… and indeed the same would apply to quote marks… I have however just experimented by created two dummy macros, one with typed string trigger xyz and the other with typed string trigger xyz (there are f…

[image] kevinb: ...one with typed string trigger... I think typed string triggers will be an absolute bugger for this, because you can't use quotes to show it's a phrase since quotes could be in the trigger... xyz will search for anything that contains "xyz" -- it isn't an exact and complete…

[image] Nige_S: You can't search for spaces outside of a phrase because space is the search term delimiter. My point is that perhaps the parsing should be such that a space is a delimiter only when not preceded by a qualifier. If, for any qualifier q:, the search terms q: and q: (or indeed …

[image] kevinb: My point is that perhaps the parsing should be such that a space is a delimiter only when not preceded by a qualifier. And to me that's broken -- a space immediately after a qualifier : should be a literal space, as per your typed string trigger example. By extension, multiple…

Thanks for your detailed reply, @Nige_S . For myself, the only obviously significant practical aspect of how : is parsed is that the likes of action: 1234 fail unexpectedly—if the user’s expectation is that the parsing will be the same as in written English. I am not however criticising the design…

[image] kevinb: Is there any logic to why the design is such that the space has to be omitted? I presume that there is (but it shouldn’t be necessary just to, say, separate search terms :thinking:). There is always logic. Sometimes misguided, but always a reason. The search string is broken …

Keyboard Maestro Discourse

Engine log - how do I find Action number # in my list of actions?

Questions & Suggestions

_jims July 4, 2026, 12:15am 13

Hi, @Ian-SAfc. Welcome to the forum!

You might find this macro helpful: Engine.log Tool

Engine log - how do I find Action number # in my list of actions?

Options