LOTW dont download

[PY2AD]

I thought it was an isolated error, but I'm having the same problem again.

QRZ downloads confirmation via LOTW, I open QLog, try to download the confirmation, and nothing comes through.

I open another logging program to test, and the download occurs.

I change the dates in QLog, it downloads a lot of old confirmations, but not the current ones. I tested it in 3 other logging programs and they all worked, which rules out any certificate or LOTW problem.

In this case: 5B4AMX

[aa5sh]

One thing I notice is you have several Callsigns. So you may need to do a download for each one changing this dropdown. But I've never tried with separate callsigns like you have.

[PY2AD]

Yes, that's quite obvious. In all programs I do it one by one, although the vast majority download them all at once.

This worked fine until the last update, then I started noticing that no confirmation was ever coming through. That's when I decided to check directly in LOTW, and it was full of confirmations that hadn't downloaded.

[aa5sh]

It may be good for you to generate a debug log. Under the Help menu there is a developer tools option. You can generate LoTW debug by using a command like this:

And you can upload here for us to take a look at. I just tested with one of my old calls and it did pull in fine so not sure what's going on:

[PY2AD]

qlog_debug_20260527230105.log

One more time, I had 1 confirmation in LOTW (my call PY5AD) from station 3V8LL, I see on LOTW site, in QRZ download, but I cannot download in Qlog. What is happening? Where am I mistake?

[aa5sh]

When was that QSL It looks like you picked 5/28/26 so the QSL would needed to be confirmed in the last couple hours. Try picking an older date in the QSLs Since date picker.

…

On May 27, 2026, at 9:05 PM, PY2AD ***@***.***> wrote: qlog_debug_20260527230105.log <https://github.com/user-attachments/files/28329897/qlog_debug_20260527230105.log> One more time, I had 1 confirmation in LOTW (my call PY5AD) from station 3V8LL, I see on LOTW site, in QRZ download, but I cannot download in Qlog. What is happening? Where am I mistake? — Reply to this email directly, view it on GitHub <#1043?email_source=notifications&email_token=AUEEMXTRQY4U7SWO6KCTN3L446NHLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQHAZTANJRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17083051>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXWSYBAAKU6RBDA5SAL446NHLAVCNFSM6AAAAACZJLV3J2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMBYGMYDKMI>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXWYWFQM2PMLN7V7DEL446NHLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQHAZTANJRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AUEEMXRSNOUSMFZBCUJ5Y33446NHLA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZQHAZTANJRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.

[PY2AD]

But why did the search method change? Before, it seemed to search for all new confirmations, regardless of the date.
It's much better if the system searches for new confirmations, and the date is just another search option, if needed.
It's impractical to have to include the date for each search, and what if there's a confirmation from 10 years ago? How will I know? Every time I download something, do I need to include the year I started my amateur radio?

[aa5sh]

The date is the QSL date not the QSO date. If you made the QSO 10 years ago but the other operator just uploaded today then the QSL date in LoTW is today. There may be a way to make he work a little better in QLog but I would like for you to verify that if you chose an earlier date for each callsign it pulls and processes fine then I or Ladislav could work up a solution but before spending time I want to make sure that is the case. Below is an live example of a QSO I made in 2012 but was just confirmed on 5/26/26.

Right now QLog just stores the last LoTW QSL download date, all logging programs do that to make it more efficient. But one thing we may need to do is store the last QSL download date for the chosen callsign in that dropdown. Not a big change really but I want to make sure it works for you before we make the change. Hope that makes a little sense. I’m trying to isolate the problem and a solution.

[PY2AD]

qlog_debug_20260528103534.log

An example.... I tried to download in various ways. ALL appears this 3V8LL, that is in my log, but dont confirm. I tried in other 2 logbooks, and confirmed.

[PY2AD]

Another thing... I have 5 different callsigns. 4 are in different Brazilian states and 1 is for Contest.

If I choose to download for PY2AD, for example, from 2020 (the initial date of this callsign), in the end it didn't check and only downloaded PY2AD.

It downloads all callsigns, some QSOs it shows as unmatched, some it confirms.

Last night, I downloaded from 2020 for PY2AD, it brought me many updates and unmatched calls.

I just did the same test, downloading from 2020 onwards for PY2AD, and it brought me more updates and 68 unmatched calls... some aren't even from PY2AD.

And if I download from QRZ, I don't get any new confirmations.

[PY2AD]

I triedseveral times, ways... but I cannot confirm the 3V8LL in 15m by PY2AD. Show me confirmed in LOTW, but Qlog dont confirm.... say unmatched

[foldynl]

If QLog reports unmatched, you need to find out why your QSO is not matching. Matching fields for LoTW are:

CALLSIGN, SAT_NAME, QSO Date -+30 minutes, MODE, Band (more details here - https://lotw.arrl.org/lotw-help/frequently-asked-questions/#datamatch)

[PY2AD]

Maybe, the problem is with LOTW.... I was seeing QSO by QSO, and really... if +-30 min, confirm just one.... same thing, if I use 2 callsigns different in +-30 min. Just confirm only one.

[foldynl]

I noticed it now. In general, it depends on how you use it, because you have the same QSO recorded with different operator callsigns. Why you do this is probably your own business, but 3V8LL is confirmed for both PY2AD and PR2AD.

However, the Download window requests confirmations only for a particular station. In the debug log, the station is PR2AD, so you also need to download LoTW confirmations for PY2AD.

[PY2AD]

In any condition, the logs download the confirmation for PY2AD.... I tried, but... dont download. I needed change manual in other log to YES, because the Qlog dont permit this changes

[PY2AD]

How can I edit this 61 confirmations in manual mode????
I need change NO to YES in LOTW received.

[foldynl]

Wiki - https://github.com/foldynl/QLog/wiki/Main-Window#qso-table - Context menu - Edit Value - "If more than one row is selected, these row are changed so that the value of the edited item is used for all selected records"