There's always a slim chance I'm wrong, because I rely mostly on reading the macros, and not testing them, but from what I see, the macro doesn't "stall", it "completes." From what I see, your macro executes the second Select action only if the first one fails. (It's hard to be sure, because you didn't upload your macro, you only took a screenshot. So I can't see the flags on your actions.)
The reason it completes is that the first menu specified in your first action now exists. That's why you are seeing the menu.
If you want the second action to be executed, you have to do what your macro says, which is not to have the first folder exist.
I've attached the macro, and perhaps that will assist more in helping me resolve the issue with my Apple Mail "Move to…" macros.
The macro is basically a duplicate of others that are nearly identical, excepting the "Move to…" folder variable.
I wish I could post a movie of this odd new KM behavior of actually showing the macro at work, opening pull-down menus, but NOT moving the associated email message.
I should have been clear that NEITHER of the steps is successful, and the macro just sits there, and -- >50% of the time -- Apple Mail also starts misbehaving, and I have to force quit it.
I assumed that the last action result being OK referred to the email being successfully migrated to the designated folder, not whether the destination folder exists.
This is new KM behavior for me, and the only systemic variable that has changed is upgrading from Sonoma to Sequoia.
I'll close in saying that this suddenly showing the pull-down menu and hanging/stalling with the message/email being moved is COMPLETELY NEW BEHAVIOR for macros that have been operating fine (and in the background, with now menus shown, etcetera) for several years. zMove To Read RESURRECTED_250302 for KM Forum 20250306.kmmacros (3.8 KB)
I don't know what "just sits there" means. Did you open the debugger? Do you see which action the macro is sitting on?
Have you ever used the KM Debugger? Do you know how to use it to see what action is being executed? Do you know how to use the debugger to go step by step through a macro?
Well if Apple Mail is misbehaving, that could explain it. There's no way for KM to fix a badly behaving application. Did you check the Apple System log file to look for error messages regarding Apple Mail? Or did you check the KM Engine log file for clues?
Also, since you didn't say, I have to ask if you have rebooted recently? I've seen some reports that Sequoia has to be rebooted one MORE time than Apple says it does.
There's no way for me to replicate the behaviour of your macros because my Mail menu can't possibly be the same as yours, since I don't have the same folders as you.
I assume that the message is moved if you make the menu item selection manually?
Then start by taking one macro and resetting the menu item choices in that macro actions. If that doesn't help, delete the "Select Menu Item" actions and recreate them.
KM can select Mail menu items just fine in Sequoia, so this is something particular to either your update (eg a subtle change in menu structure from the previous version) or your system.
I'm grateful to Airy and Nige_S for their insights.
To Airy: yes, I have used the debugger, and it usually confirms what I am experiencing: the macro "hangs", "just sits there", "stalls" or whatever seemingly irritating description I use to describe the point of fail.
To Airy and Nige: I went for the President Musk option and defenestrated the macro. Perhaps it was carrying with it some bad juju from the macros it was borne of via duplication?
FYI: prior to recreating the macro from scratch, I reindexed Apple Mail and a host of other perfunctory directory structure and permissions housekeeping, rebooted from a FULL SHUT DOWN (which our engineers advise, as a RESTART apparently keeps debris "alive" in RAM).
Upon recreation of ostensibly the same macro (atttached), everything is back to behaving as it should (as much as I can tell).
I still "see" the macro steps taking place in the menu, etcetera, but they are "behind the scenes", and the pull-down menus no longer make unwanted appearances (quite a mess of cascading folders).
I reiterate my appreciation for the collective insights.
