I wanna chime in and say I was having similar issues, and I am also an ex-Lexicon user. I have come to believe that some 3.2.0 users that use (or previously used) Lexicon are being affected by a similar bug that affected people in 3.0.0 (though that bug was more fatal! this one is sneakier).
Lexicon alters the Engine database and doesn’t always play nice, particularly when Engine updates.
I hit up the Lexicon Discord for help and the admin/owner suggested a newer version of Lexicon might fix the issue. I told him I wasn’t interested in re-subscribing, only resolving a bug I believe his software introduced. Was hoping he’d offer to make things right. He insisted I re-subscribe. Pretty awful, predatory business model imho.
In any case, I bit the bullet and re-subscribed and the newer version of Lexicon did indeed fix the bug, which to me only offers further affirmation that the bug was introduced by his software. Don’t recommend supporting him if you can help it, but if you’re having similar issues to me, it might be your best recourse.