Side effects/problems when upgrading Sequoia

Just upgraded to Sequoia 15.2 and am now getting Numeric condition failed to get text from source
in Engine log.
The macro has executed ok, and this looks like something that is happening after macro has finished.
Update:
Happens after different macros.

Can you upload an example Macro?

1 Like

No need to upload macro, as some were really trivial e.g.

Screenshot 2024-12-13 at 17.49.07


1: Added KM to System> Security>Input monitoring. Still had problem.
2: Did Restart KM Engine. Quit and restart. Still had problem.
3: Logged user in and out. Still had problem.
4: Complete shutdown then restart.
Problem went away. :slight_smile:
Go figure??

Not having issues with KM is the only reason I haven't updated to Sequoia yet. Did you have any other similar issues?

It was late one night and I thought I was upgrading Sonoma, but it fact it was a full upgrade to Sequoia,

So next morning I just bit the bullet. (Even though I could have reverted to my full backup)

I then had to review all my apps for compatibility.

While 99% ran ok, it was clear that a lot of software houses viewed Sequoia as a major leap, and therefore you were “advised” to upgrade to the “latest” Sequoia compatible version. Carbon Copy Cloner was one that I felt was prudent to upgrade.

We are now on 15.2 so most of the howlers have been fixed.

Personally I would wait till

A: you had to upgrade

B: release 15.4 is out and/or it is June 2025.

Bottom line, If everything is working fine now, don’t try and fix it.

1 Like

I'm seeing this too now, and I'm still on 15.1.1 (upgraded to Sequoia on 29 Nov). This strange log message only first appeared less than an hour ago, often it's followed by Last message repeated n times (n has ranged from 2 to 141 times). Also happens after different macros with no apparent rhyme or reason.

1 Like