Applescript Trigger by Name or UUID Produces Error

[sp737]

I am not that good with KM - you have been warned

Experimenting with Hazel and Applescript to run a macro based on the name or UUID. When run I get an error (see below). I used the 'Copy As' menu function to obtain the UUID, and the macro name was copied from the title of the macro.

That's where I'm at... seems as though it should work?

-- ignoring application responses
tell application "Keyboard Maestro Engine"
	do script "Save Attachments of Selected Message v1.10"
	-- or: do script "F03C712A-D330-42A9-BF6E-2A7998B199F4"
end tell
-- end ignoring

[Tom]

Just tested it with an arbitrary macro (from Script Editor, I don't have Hazel) and it works fine, by name or ID.

the macro name was copied from the title of the macro

You can copy the whole launcher script (including name and ID) from the Script trigger:

[sp737]

I just copied the whole launcher, ran it in the script editor... with the same error:

[Tom]

Weird. Have you tried relaunching KM Engine? Maybe it has messed up the registered macro names or something…

You can quit and launch KM Engine from the KM Editor menu (File > Quit Engine | Launch Engine).

[tiffle]

You need to pay attention to the error message. Make sure:

• the macro is enabled
• the group the macro is in is enabled and active

Have a look at this discussion for the same problem.

Subroutine to Get List of All Macros and IDs in a Specific Macro Group

hello @tiffle ! my apologies for the delay. Your macro is fantastic. Extremely useful. My problem is that it works with some macros and others not. KBM Engine: 2024-02-21 16:52:46 Action 15561165 failed: Execute an AppleScript failed with script error: text-script:150:169: execution error: Keyboard Maestro Engine got an error: do script found no macros with a matching name (macros must be enabled, and in macro groups that are enabled and currently active). (-1) I suspect that it has somethin…

[sp737]

I did take a look at that thread - - thanks. However, both the group and the macro are active.

Just discovered what my problem was! I had the macro set to be available in the mail application ONLY. So, of course the script editor could not run something it did not have access to.

Thanks for the assist!

[tiffle]

@sp737

So, of course the script editor could not run something it did not have access to.

Well that's just another way of saying while you were testing in script editor your mail macro group was not active and so no macros in that group would be able to execute.