Hi, @anamorph.
Yes, I think many users have encountered the same issue. I assume you are primarily referring to hot key triggers.
One thing you can do it just assign the preferred hot key, try it and see if there's a conflict. Often when I do that, I find a lesser-used macro and I do one of the following to that macro:
- Disable the macro
- Remove the conflicting trigger
- Change the hot key
Occasionally I even delete the conflicting macro.
BTW, the Trigger Macro by Name action and the Alfred Workflow Conductor are great options for macros that are used less often.
Now, to get a bit into the weeds...
I've shared two macros that I use to assist when I encounter a hot key conflict. Here's my workflow (YMMV!):
- With the new macro, assign the preferred hot key.
- Press the hot key.
- Assuming there's a conflict, a Conflict Palette is displayed.
- Assuming that the conflicting macro is innocuous, run it. Then run Edit a Recently Executed Macro to quickly navigate to the conflicting macro.
- If running the conflicting macro is not a good option, use Search All Macros to navigate to it. (Alternatively one can use the Keyboard Maestro Editor Search field (upper-right) or a Smart Group both with the Search Strings suggested by @Airy).
- As mentioned above, for the conflicting macro: disable it, remove the conflicting trigger, change the hot key, or delete it from my library.
- Using the Keyboard Maestro Editor Back button (in the History group), return to the new macro.
Okay, back out of the weeds. ![]()