I've also seen this.

Have gone back to 2.6.1.0, waiting for 2.7.1.0 (or 2.8.0.0).

I am running 2.7.0.0 on Win 10 Professional, and I am also seeing this same issue.

With 2.7.0.0 I have the opposite problem!

Up until now WSJT-X QSO''s showed up with LOTW SENT status as "Requested". Suddenly they show up as "No" and do not upload.

I agree with John.

You got this exactly right!

Thanks.

I found my error.

"Import QSO from JT Message #12" was not checked.

All is well.

Recently had a computer crash, so have rebuilt Log4OM in a new computer, along with WSJT-x. I have the two programs connected via UDP, but Log4OM isn't logging the FT8 QSO. When I start a QSO in WSJT-x, the "entry" and info areas in Log4OM reflect the ongoing QSO. Callsign field is populated, and in...

I am using Log4OM V2.6.1.0 and Windows 10, current rev level. I operate using two monitors. My logger (Log4OM) is kept on the #2 monitor, off to the right side of my operating position. But it doesn't stay there between sessions. Each time I launch, it comes up in the main (#1) monitor, and I must ...

My shack computer is provisioned with two monitors. A "main" screen in front of me, and a second "logging" screen off to the right. The second screen is where I run Log4OM. I would like that assignment to be "sticky", to be retained at shutdown. Then I would like Log4OM to appear where I left it whe...

New information relative to this issue: This evening I ran a hundred or so CW QSO's, feeding Log4OM from N1MM+. All QSO's from N1MM+ were recorded on Log4OM with the CORRECT CQ zone. Then I went to FT8 (WSJT-x) for a few QSO's. Several of them were recorded as Zone 0. Another tidbit: I upload all Q...

FWIW, I use WSJT-X and JTAlert, and I have never had a Zone 0 entered in my log from that combination. I don't normally use lookups from QRZ, HamQTH, etc. I do not use JTAlert, and I do use QRZ XML for lookups. My WSJT-X contacts are fed to Log4OM via UDP connection. Almost all USA contacts, and oc...