You are welcome.
I didn't examine all your macros, I just spotted the one problem at the end of your macro. I might take another look tomorrow.
Just to pick up on this bit:
When your "Main" macro executes the "Execute Macro 'Header'" action, "Main" pauses until the "Header" macro completes -- only then will "Main" continue on to its "Cancel" action.
This is why your macro count is rapidly stacking up -- each "parent" is waiting for its "child" to complete, that "child" is waiting for its "child" to complete, and so on.
You can solve some of this by setting those "Execute a Macro" actions to run "asynchronously" (the default is "synchronously") -- the "child" macro is then executed separately and "Main" can continue without waiting for them to complete. But you can easily get into a situation where your now-separated macros are "competing" with each other, so you may need to reconsider your entire flow logic.
Many thanks to all of you for your help. @airy, I have studied your macro very closely and have come to the conclusion that the method with the state variable is the best and also a very interesting variant for me. I have now created a trigger macro that can be triggered with all the keyboard shortcuts that I need. And depending on the shortcut, the state variable is changed and then the corresponding macro is executed. If I need a different macro, I set the state variable to the value that I need and the correct macro is executing after the previous one has finished or canceled. That's exactly what I wanted. Thanks again for your help.
Ronny
You are welcome. I use the state variable approach a lot lately. Sometimes it really helps, although sometimes it's not the best solution. But if you like it, use it.