Amazing!
Thanks!

I have already.

Where I think the problem may be is in a migration late last year.

But that would be a database hiccup, and I am unsure how your plugin stores such information if at all.

Interestingly I can use both sets and they work as intended. I simply use the second set out of uniformity.

However, if it is processing this on an administrative end, what is it slowing down on the front end?

Odd issue, but I would like to resolve it for optimization sake, especially since our website is a 501(c)3 non-profit and one day someone else will inherit this quirk if we remain with your plugin as we currently intend.