Log4OM

I have browsed through multiple topics of trouble with lookups to QRZ.com.
Many of the answers were about being a HAM member of QRZ.com and not an XML subscriber.
However, most of the problems seem to be caused by fast input of callsigns using UDP from other apps such as WSJT-X. The person confirming the phenomenon must have probably entered the call sign by hand, letter by letter. The problem is not related to the member type of QRZ.com.
I would like to ask Log4OM to avoid problems caused by the large number of characters in call signs.

The 2.32.1.6 beta fixes have resolved some of the issues, but not others.

"8J7KJ4O/7" now searches and displays QRZ.com properly. However, the callsign field for "8J4Y70A/P" remains blank. The only difference is whether or not you're registered with QRZ.com.
When I manually paste "8J4Y70A/P", the callsign is pasted but it doesn't search for completed QSOs.
I think it should be displayed in "Worked before" since there is an actual QSO log.

But thanks.