Lookup error - needs refresh action

By mistake, I type VK2I.
PoLo looks up VK2I in my Call History file and returns a name, and fills in the QSO.
But it’s a mistake, so I correct it, backspace out I and 2, then add VK3IMD which is what I wanted.

There is no Call History for this call, nor is there any QRZ record for it.
IMO, the QSO should be blank, no name no details.
But it remains as per the lookup from Call History for VK2I

There appears no way to clear and or correct this QSO in these circumstances.
If I do a “Lookup all QSOs” it remains incorrect because there is no QRZ return for it.

And further, now that this erroneous entry is in my log, it continues to pull in the incorrect name for VK3IMD. Even if I delete the entry and try again with the VK3IMD, it pulls in the wrong name from what appears to be a deleted incorrect QSO record.

Unless you can think of another way, I think there needs to be a way to just clear the QSO of details.

I had this happen twice today - also with VK2PTT (no QRZ record yet), but it pulls in VK2P from Call History and will not allow to get rid of the wrong name and other details.

Alan

If I turn QRZ back on, I can get the correct name to replace the error for VK3IMD
And the wrong name for VK2PTT which has not been updated on QRZ.

I was hoping to do without QRZ, but the call history lookups appear to be “shorting” like the QRZ lookups used to do some time ago.
Alan

One reason you see some of this behavior is that all these call lookups are cached in memory.

I’m changing it so that the cache is cleared after each new QSO is logged.

Also found another subtle bug that should fix this scenario you ran into.

At this point it will most likely go into the February release, since this is not a critical bug.

2 Likes

No worries - thanks for the response.
Alan