How to tell which macro called another?

Questions & Suggestions
1

I see Debugger Breakpoint actions. How are these used?

I have a macro that is getting called inexplicably. How could I find out what is triggering it? I realize there are many possibilities and some are the kind I couldn’t catch, but maybe some kind of break point would help.

1 Like
2

Add a Set Variable To action as the first action, and set it to the trigger info.
Then display this Variable, or view it in the KM Preferences.

2 Likes
3

That is deep. Ridiculous what’s in KM.

1 Like
4

Would you please retitle this. It doesn’t really have anything to do with debugger breakpoints. I suggest “How to tell which macro called another?”

1 Like
5

Changed as requested.

1 Like