Yes, that's what I mean.
That's what I've been doing, and maybe because all my macros are either done manually via a shortcut or they have the "activate application" action, I've never experienced that error until yesterday.
I haven't tested with a macro that only contains AppleScript. This particular macro is just a few "normal" KM actions to rename some files, no AS alone.
I think this is the perfect scenario where having Folders instead of just Macro Groups could be handy. I could have a folder called Finder (instead of a Macro Group) and inside I would be able to have multiple macro groups, all focused on macros for Finder, but where some are "global" and some are "application restricted".
Since that isn't possible, now all macros that are application specific, but I want to run in the background, need to go to a global macro group, making that group a huge mess.
Everything could be well organized if folders were implemented. Unfortunately that doesn't seem to be something that will be implemented, according to a thread someone started a while ago and Peter doesn't seem to see the value of that.
Thank you for answering my question and clarifying that for me.