Dup calls and error after LOTW download

[k4em]

Both QSO's were logged and it looks like LOTW accepted both QSO's, because of the "NEW CONFIRMATION messages". So how do I get rid of the "Warn: MULTIPLE QSO UPDATE" messages.

08:39:29: WARN: MULTIPLE QSO UPDATED: Callsign: SP8U Date: 10/15/2020 11:58:00 AM Band: 20m Mode: FT4 by Callsign: SP8U Date: 10/15/2020 12:07:00 PM Band: 20m Mode: FT4
08:39:29: [3] *** NEW CONFIRMATION [Poland] Callsign: SP8U Date: 10/15/2020 11:58:00 AM Band: 20m Mode: FT4 ***
08:39:29: WARN: MULTIPLE QSO UPDATED: Callsign: SP8U Date: 10/15/2020 12:07:00 PM Band: 20m Mode: FT4 by Callsign: SP8U Date: 10/15/2020 12:07:00 PM Band: 20m Mode: FT4
08:39:29: [3] *** NEW CONFIRMATION [Poland] Callsign: SP8U Date: 10/15/2020 12:07:00 PM Band: 20m Mode: FT4 ***

It would be nice if LOG4OM2 could flag these BEFORE an update (possible dups) so we could correct the dups before the upload.

Thanks,
Dave
k4em

[G4POP]

The question is how did you create dupes in the first place?

Looking at the time difference I am guessing that you are sending the qso's via UDP from the JT program and ALSO using ADIF monitor.

So re-configure your LOG4OM settings as in our user manual and also delete the duplicate entries