QRZ Lookup problem.

[va3cp]

I have noticed since I upgraded to RumlogNG V5.11.4, the QRZ lookup seems to hang or takes a very long time. If I click over to HamQTH and back to QRZ.com on the "Log Station Info" window, the name is there instantly.
Late 2021 27" iMac
MacOS Monterey V12.6.2
Rumlog NG V5.11.4

Tested on my 2011 MacBook Pro
OS X High Sierra V10.13.6
RumlogNG V5.6.9.

MacBook brought up the QRZ search in less than a second.

Anyone else seeing this?

[DL2RUM]

There is a time delay of two seconds. The query starts two seconds after tabbing out of the callsign field. This was introduced after some trouble end 2022.

[va3cp]

Thanks Tom,
I have not restarted my iMac and I see the 2 second delay today on all lookups. Maybe there was a temporary problem with QRZ yesterday.
Thanks for your quick response as always.

[va3cp]

Tom,
Just discovered some more information regarding QRZ lookups. If I try to look up the same callsign for two QSO's in a row, the second QSO does not populate the QRZ information. I have to go to HamQTH and back to QRZ on the "Log Station Info" window and then the QRZ info is retrieved instantly. I tried this with several different call signs and got the same results.

[DL2RUM]

Yes, that’s the way it works currently. It‘s by design.
Why do you have to look up the same callsign twice?

[va3cp]

Tom, I frequently log the same call sign multiple times in a row when they are activating for Parks On The Air and change bands or modes or are operating from a different park entity. Last night, I logged KE8PZN on 40, 60 and 80m SSB and 80m CW.

[DL2RUM]

See, and then you want to transfer all relevant data to the log?

[va3cp]

I am hunting Parks On The Air (POTA) stations from home and it is common for the activator to change bands or modes which gives them credit for additional contacts. They may also go to multiple parks in the same day and if I work them at a different park or on a different band or mode, that counts as a new QSO with regards to POTA. This is why I sometimes end up logging the same call sign multiple times in a row.

Now the I know this is designed into the program, I know how to work around consecutively callsign lookups.

[DL2RUM]

Thats's a legitim use case. I will find a solution.