KM very slow and laggy after Sonoma upgrade

[Mircea.M]

I have upgraded to Sonoma, simple macros like window manipulation are taking a lot of time (2 sec - 3 sec). I have uninstalled KM and inslalled back again, did not resolved the issue. I had to put extra PAUSE times in my macros for making them work again, and I have a lot of macros. This update was not good, it s the first time that I have encountered this type of behaviour in KM.

Does anibody foud a solution for this situation.
Sonoma 14.2.1 with M1 Max, 64 Gb RAM

[cdthomer]

The window manipulation issue is a fairly well-documented one, dating back at least a couple of years. Sonoma seems to have made the matter worse however.

• Window resize works inconsistently (dependent on App and Mac) - Questions & Suggestions - Keyboard Maestro Discourse
• Possible Bug: Manipulate a Window Interacts Differently (And Unreliably) With Different Applications - Questions & Suggestions - Keyboard Maestro Discourse
• Getting Started with macOS Shortcuts - Questions & Suggestions - Keyboard Maestro Discourse

Anyhoo, note Peter's comments on one particular post:

Getting Started with macOS Shortcuts

Yes, sadly the Accessibility API has a nasty habit of simply ignoring part or all the request to change the window. Apparently there are apps that can make this worse or better by turning on or off an undocumented accessibility parameter. As it is, Keyboard Maestro already executes the Accessibility requests multiple times when making the changes. One thing to try is to simply add a Repeat action around the Manipulate a Window action (and maybe a small Pause as well) and repeat the action 3 t…

Make sure you are up to date with the latest KM version as he implemented a workaround to mitigate the crappy Accessibility API (which is posted somewhere else on the forum but I can’t find it right now).

[Mircea.M]

Thank you for your answer, until Sonoma everything worked fast and snapy, I am 100% sure that Sonoma is the reason. I have used KM 11 on before Sonoma and it was ok. We are hoping that the issue will be resolved in next OS.

Thank you!