Since the upgrade to v2.36.1.0 LoTW uploads have stopped working.
When Log4OM is closed the shutdown hangs (forever) whilst the LoTW upload tried to take place; when I try and push the uploads manually Log4OM just stits there trying to upload through TQSL.
Certainly something wrong with your set up because it works fine for me as confirmed below
INFO: ADIF File created successfully.
INFO: TQSL Version 2.8.1
No private TQSL Password set
Executing TQSL with upload
MANAGED MODE SET
Messages from LOTW:
TQSL Version 2.8.1 [v2.8.1]
Signing using Callsign G4POP, DXCC Entity ENGLAND
Attempting to upload one QSO
D:\Google Drive\G4POP Log4OM NG\config\LOTW\LOTW_UPLOAD_20250613191114.adi: Log uploaded successfully with result:
File queued for processing
After reading this message, you may close this program.
Final Status: Success(0)
success; log signed and uploaded and accepted without incident
INFO: SAVING LOG...
INFO: LOG SAVED
LOTW END
Check the firewall and anti virus are not intervening or perhaps something set wrong in TQSL
The last QSO marked as sent to LoTW is on the 15th May, after that, none are marked as sent. But LoTW has them, and I just proved that upload is working by checking LoTW.
But Log4OM is just sitting and waiting for something, which I'm not sure how to debug unless there's a verbose log somewhere that I can look at.
I'm going to mark all QSOs as sent and see if that makes a difference.
I've upped the logging level. LoTW has worked flawlessly in the past, and I've not had 'TQSL Interactive mode' ticked. So I'll do some more testing with all of that and come back with my findings.