I have encountered this situation twice, and the two instances were different. In one case, the RST signal I received was significantly later than my TX1, but the connection seemed to have been established. However, my automatic QSO start time was recorded as the RST time, while the other party may have used the TX1 time for their calculations, resulting in a mismatch. The solution was to search for the relevant connection log in JTDX's all.txt file and then determine which time was correct. Since RR73 is essentially a successful connection, the issue was likely due to an error in the automatic program. This correction would not affect the validity of the QSO. In the second instance, the other party incorrectly entered their QSO start time, resulting in a one-hour delay. I directly rejected their submission and asked them to verify the time.