cqrlog is attempting to use the 'realtime' single QSO upload method to do bulk uploads to Clublog.
This is explicitly banned by Clublog because it causes too much traffic.
An example:
I enter a contest and make 140 QSOs. As I make each QSO it is uploaded to Clublog - this is okay.
After the contest I upload the QSOs to LotW - this causes the QSOs in cqrlog to be marked as updated.
Next time cqrlog does a Clublog upload (either because a new QSO happens or because the menu item to do a Clublog update is used) Each updated QSO is deleted and re-uploaded to Clublog using the realtime interface. After about 25 QSOs this causes Clublog to give an "Access Denied" message and lock the user out for about 1 hour.
See the Clublog Help info at:
https://clublog.freshdesk.com/support/solutions/articles/3000023706-exce...
https://clublog.freshdesk.com/support/solutions/articles/54905-how-to-up...
https://clublog.freshdesk.com/support/solutions/articles/3000110752-ip-a...
73 Colin G8TMV
Hi Colin!
Online logs are not my favorites. I do not use any and so have no way to test.
If I understood right making LoTW upload to qsos already sent to online logs causes reupload to online log.
May I ask have you tested this?
--
Saku
OH1KH
I have not tried it yet. But I will do.
*However* In the case of Clublog I actually need to upload the changes so that Clublog knows that the QSO's have been uploaded to LotW so that it can take account of this when suggesting QSL status.