DXCC Invalid Alert

Yes, sometimes it happens... Please report any bugs here
Post Reply
w9mdb
Old Man
Posts: 199
Joined: 13 Jul 2014, 12:05

DXCC Invalid Alert

Post by w9mdb » 13 Feb 2020, 17:39

Helping a friend with this problem....
Log4OMv1 emailed a DXCC alert for TO4A -- but it looks like it failed the lookup (country is blank) and still sent an alert. Is it possible when the country is blank it's passing some logical check like with DXCC=0 not matching anything in the log? I guess the QRZ lookup failed for some reason but didn't have enough debugging to see that action.

2020-02-13 14:42:39.0866 INFO: SharedFunctionsManagement: INTERNET CONNECTION ACTIVE
2020-02-13 14:44:02.1863 INFO: TCPEventManager: MAIL SENT TO COMMUNICATOR: 8023381851@VTEXT.COM SUBJECT: New Spot from Log4OM BODY: [2020-02-13 2:44:02 PM UTC]
Source Cluster
Callsign: TO4A
Country []
Spotted on 21021.0 (15m) on mode CW by W1NT from NA [loc ]
Note: CW 11 dB 33 WPM CQ
Rule Matched: DXCC Log4om
2020-02-13 14:44:02.1965 INFO: #=qS1uvrNwTfj2_4pd9cI2csPMnkBllXP8ySezYQKsL_dk=: Log4OM desk notification sent [2020-02-13 2:44:02 PM UTC]
Source Cluster [Rule: DXCC Log4om]
Callsign: TO4A
Country []
Spotted on 21021.0 (15m) on mode CW
Note CW 11 dB 33 WPM CQ

Post Reply