HamApps Support (VK3AMA)
On 11/02/2020 11:42 am, Paul-N5DUP wrote:
This has been discussed many times.
This error message indicates that JTAlert was unable to confirm that the QSO was successfully logged. It does this by performing a direct read of your Loggers log file/database. JTAlert doesn't rely on the logging status produced by some loggers which have shown to incorrectly indicate successful logging even when failing to log the QSO. Also some loggers don't provide any feedback at all when logging via their API, so JTAlert always tries to confirm success/failure via a direct log/database read.
If the QSOs are indeed getting logged you will need to increase the "Check QSO Log Record" time. See the Logging section of the JTAlert Settings window.
Very likely the post logging activities being performed by your logger are being impacted by Internet access speeds resulting in later than normal logging. Typical examples are post logging XML lookups or posting the QSO to online logs.
de Laurie VK3AMA