I don't think we have to do anything. But if you see a lot of new QSLs that aren't really new....

------- Forwarded Message -------
From: Jon Bloom, ex-KE3Z <jon@3blooms.net>
Date: On Monday, August 25th, 2025 at 07:59
Subject: [ARRL-LoTW] LoTW QSL fix
To: ARRL-LoTW@groups.arrl.org <ARRL-LoTW@groups.arrl.org>

> It was reported that some LoTW QSL records showed "Invalid date" for the QSL date/time. In tracking this problem down and fixing it, a logical error in LoTW was discovered.
>
> This error occurred when a QSO record that QSLed another record was replaced because something in the station location changed. For example, if a user corrected his grid square and re-uploaded the log, the QSO record would be replaced, and any VUCC award credits based on the previous data would be changed to reflect the new grid-square value.
>
> This sometimes caused the QSL date/time to become invalid, but even when it didn't the QSL date/time remained at the previous value, the date/time of the original QSL match.
>
> This is problematic because a download of "QSLs since some date/time" would not reveal that an existing QSL record had potentially changed its station-location data. So for the example above, the other user's records may show that the original grid square was worked, although that value no longer exists, and would not show the new grid square.
>
> This logic error has been corrected in LoTW going forward, but it remains to back-fill the missing QSL date/time values in the database.
>
> Before we do that, I wanted to give people (especially authors of logging software) a heads-up that after that's done users may see a lot of "new QSLs" that are actually replacements for QSLs previously reported.
>
> I anticipate making those updates to existing records within the next day or so.
>
> Once this is done, LoTW should reliably report as a new QSL not only newly formed QSLs, but also ones whose location values have changed.
>
> -- Jon
>
>