Log4OM

2E0GJH wrote: 14 Jul 2020, 09:29 Hello Terry,

In this case mostly WSJT-X, although it may have happened with a direct entry of the QSO in Log4OM v2 as well.

No I need to know exactly the source of each of the QSO's for the ones that are correctly marked and also the ones that are not

2E0GJH wrote: 14 Jul 2020, 13:53 OK Thanks Terry,

For what it’s worth, I’ve just done 8 entries via WSJT-X and all have behaved properly. I wonder if one of the online services is perhaps occasionally returning an unexpected response leading Log4OM to believe the upload was unsuccessful.

Is there any diagnostic logging I can turn on for the external services?

Yes

Help/Log Level and select debug

OK will turn logging on and see if I can reproduce the failure. Just to try and provide some clarity here (it seems however I write this confusion is persisting) - you said:

“No I need to know exactly the source of each of the QSO's for the ones that are correctly marked and also the ones that are not“

I want to be 100% clear - at the point of entry into Log4OM **all records are marked correctly**, regardless of direct, wsjt-x or Fldigi. The problem occurs after a few minutes when Log4OM has attempted to send the record to Clublog/HRDLog when the sent confirmation status of the QSO is not updated correctly.

2E0GJH wrote: 14 Jul 2020, 14:25

I want to be 100% clear - at the point of entry into Log4OM **all records are marked correctly**, regardless of direct, wsjt-x or Fldigi. The problem occurs after a few minutes when Log4OM has attempted to send the record to Clublog/HRDLog when the sent confirmation status of the QSO is not updated correctly.

I understand that, but I still need to know the origin of the QSO's for both the bad and the good records

At this time I dont know if the ones being incorrectly marked were by a manual entry direct into Log4OM or if they were being received by UDP, ADIF import, XML/RPC or what, I need a starting point!