I uploaded both to Clublog and LOTW. Not sure why the date or time may be wrong in CW. So I am trying to find out if there is another case like this.
Ignacy NO9E
Here's a possible cause:
Most ADIF processing, including LOTW and Clublog use the TIME_ON field to determine the QSO time match. (It uses QSO_DATE also, but that's not a problem here).
If your logger "started the clock" from the moment you entered the call into your logger at the start of your pileup journey and didn't log it until you worked it, as you yourself requested, your TIME_ON will be from the moment you entered your pileup TIME_OFF will be when you actually
worked and logged the station. General purpose loggers don't know the difference between a long rag chew and sitting in a pileup.
The TIME_OFF field will reflect, pretty closely, the actual time you worked the DX. Maddeningly, however, almost all software processing ignores that field. So, as far as LOTW or Clublog or anyone else is concerned, you are claiming to work the DX as of the moment you
entered the pileup. Dumb, but that's the way code works.
So, if you (say) sat in the pileup for 45 minutes, your TIME_ON field will be 45 minutes earlier than the TIME_ON for the DX. Clublog will not match a time difference that large. I believe the difference is 15 minutes for Clublog, 30 minutes for LOTW.