Restoring macros from backup...but the .plist file is out of date

Questions & Suggestions
1

Hey folks, I've got a bit of a strange problem here. I've just done a drive wipe, upgraded my OS to Sequoia, and restored everything off my cloned backup drive. I'd updated the backup drive right before the OS install, but when I went to open KM, there were only a handful of macros in there. I then went to the Library/Application Support/Keyboard Maestro folder on the backup drive, and the macros file in there is five years old, despite my having tons of macros created over the last few years, and they were still in KM a few days ago. I've also checked my Time Machine, spot checking that folder over the last year or more, and it's the same, the newest files are at least five years old.

It seems weird to me that both the Time Machine and the cloned drive would show old files in there, which leads me to believe that they must've been stored somewhere else. Since I've got an updated clone of the drive made when it everything was working fine, I'm hoping that they're in there somewhere, but Spotlight searches aren't bringing up anything newer if I search for Keyboard Maestro Macros. Spotlight is still indexing, but at a snail's pace so it could be a while before the whole index is built.

So it's a bit of a long shot, but can anyone suggest any other places I might look?

3

Hey cherry44scott, thanks for the reply. It's possible that it was the sync or something like that, it's also possible that it was entirely user error on my part. Either way, I was expecting to find them in Macintosh HD/Library/Application Support/Keyboard Maestro, but they ended up being in Macintosh HD/Users/myusername/Library/Application Support/Keyboard Maestro. I guess with Spotlight not being entirely indexed it wasn't finding that folder. In the end, everything's working, and I was able to breathe a little easier and unclench.

4

Keyboard Maestro macros are stored in ~/Library/Application Support/Keyboard Maestro.

If that is out of date, then that was not the account you were using Keyboard Maestro on.