By other actions? No. By me? Absolutely.
As you probably know, any references to macros in KM are by the macro’s UUID (unique identifier), which is why, when you change the name of a macro, all references to it change also.
So having more than one macro with the same name is OK, as far as KM is concerned. If you have any AppleScript or JXA code that relies on the macro’s name (which you shouldn’t), then that could be an issue.
This can get dicey if you do the following, which I’ve done more than once:
- Duplicate a macro, so I can keep the original version while making changes.
- Change the “copy” macro, and get it working.
- Delete the original macro, and rename the “copy” macro.
If the macro was used as a sub-macro, you just broke your references to it. Moral of this story is to save a copy, that’s always a good idea, but make your changes in the original version (unless it’s on a timer and might get launched while you’re working on it, in which case, you’re on your own).
Probably more info than you wanted, but that’s better than less, right?