Cluster alert band not confirmed is broken

[w9mdb]

"not confirmed band" in the Alert Management is not allowing new dxcc on band when a non-confirmed QSO is already there.

In Test#1 below we do BA5CJ 80M CW with no prior 80M QSO in log. It works and we get alert audio and email.
In Test#2 we add BA5CJ 80M CW to log unconfirmed -- then spot it and it does not alert as expected.
In Test#3 we then spot BA5DX -- but it does not alert in cluster, audio, or email like it should since it's a new call on China and 80M China is not confirmed

Test#1 -- works

Worked when there was no prior 80M QSO at all

2024-02-06 15:50:23.9710 DEBUG: [dje_z9U8QJS9HFVVKEZ7U8D9Q3S2FN9UQ_ejd][MoveNext] : SPOT mode overriden to CW
DX de WA1SXK: 3573.0 BA5CJ CW 1550Z
2024-02-06 15:50:23.9710 TRACE: [dje_z9U8QJS9HFVVKEZ7U8D9Q3S2FN9UQ_ejd][MoveNext] : Cluster ranking search: DXCC 318 China -> 282
2024-02-06 15:50:24.0427 INFO: [dje_zSZJWFVUJ2AVJUPCHUW9TQ_ejd] : [CLUSTER ALERT] Sending e-mail
2024-02-06 15:50:24.0437 INFO: [dje_zZ9T46NMVPQW5E37LL8HWETV6TYSA_ejd] : Sending e-mail to 8023381851@vzwpix.com
----------------------------------------------------------

Test#2 -- works as expected

Then add BA5CJ 80M worked -- not confirmed
2024-02-06 15:58:27.0544 TRACE: [FormClusterManagement][dje_zQ8KLETC3VA5XEZFY58NCW_ejd] : CLUSTER: 2024-02-06 3:58:27 PM : [Simulation] DX de WA1SXK: 3573.0 BA5CJ 1558Z
2024-02-06 15:58:27.0604 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : Performing QSO search on callsign BA5CJ
2024-02-06 15:58:27.0604 DEBUG: * [Countries][SearchCallsign][22420 ms] : Performing Search Callsign on call BA5CJ on date 2024-02-06 3:58:27 PM
2024-02-06 15:58:27.0750 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : No Clublog CQ ZONE found for BA5CJ
2024-02-06 15:58:27.0769 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : Searching clublog exceptions
2024-02-06 15:58:27.0780 TRACE: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : No Clublog exceptions found for BA5CJ
2024-02-06 15:58:27.0780 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : LOTW user identified
2024-02-06 15:58:27.0780 DEBUG: * [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext][17 ms] : QSO search on callsign BA5CJ completed
2024-02-06 15:58:27.0790 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call BA5CJ on date 2024-02-06 3:58:27 PM
2024-02-06 15:58:27.0869 TRACE: [ProgramStorage][GetFlag] : Flag CHN identified.
2024-02-06 15:58:27.0869 DEBUG: * [Countries][SearchCallsign][7 ms] : Performing Search Callsign on call WA1SXK on date 2024-02-06 3:58:27 PM
2024-02-06 15:58:27.0969 TRACE: [dje_z9U8QJS9HFVVKEZ7U8D9Q3S2FN9UQ_ejd][MoveNext] : Cluster ranking search: DXCC 318 China -> 282
2024-02-06 15:58:28.9401 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for GI3TME
2024-02-06 15:58:28.9401 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for N9XA
2024-02-06 15:58:28.9411 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for OH0Z
2024-02-06 15:58:28.9411 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for KK8A
2024-02-06 15:58:28.9421 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for 9A2HB
2024-02-06 15:58:28.9421 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for YU1VDG
2024-02-06 15:58:28.9431 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for DM2BRF
2024-02-06 15:58:28.9431 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for I2VIU
2024-02-06 15:58:28.9431 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for DL5ANT
2024-02-06 15:58:28.9441 TRACE: [WorkedBeforeManagement][FindWorkedBefore] : [WORKED BEFORE] Begin search for BA5CJ
---------------------------------------------

Test#3 -- does not alert on BA5DX even though 80M China is not confirmed.

Spot BY4DX -- expect alert to happen since 80M China is not confirmed and we have "not confirmed band" in the Alert Management
2024-02-06 16:00:47.6947 TRACE: [FormClusterManagement][dje_zQ8KLETC3VA5XEZFY58NCW_ejd] : CLUSTER: 2024-02-06 4:00:47 PM : [Simulation] DX de WA1SXK: 3573.0 BA5DX 1600Z
2024-02-06 16:00:47.6997 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : Performing QSO search on callsign BA5DX
2024-02-06 16:00:47.6997 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call BA5DX on date 2024-02-06 4:00:47 PM
2024-02-06 16:00:47.7126 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : No Clublog CQ ZONE found for BA5DX
2024-02-06 16:00:47.7156 DEBUG: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : Searching clublog exceptions
2024-02-06 16:00:47.7167 TRACE: [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext] : No Clublog exceptions found for BA5DX
2024-02-06 16:00:47.7167 DEBUG: * [dje_zV8NHHZ3ZC8FRW5SC3JTN878MKYZRJLHLJ2_ejd][MoveNext][16 ms] : QSO search on callsign BA5DX completed
2024-02-06 16:00:47.7177 DEBUG: * [Countries][SearchCallsign][16 ms] : Performing Search Callsign on call BA5DX on date 2024-02-06 4:00:47 PM
2024-02-06 16:00:47.7256 TRACE: [ProgramStorage][GetFlag] : Flag CHN identified.
2024-02-06 16:00:47.7256 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call WA1SXK on date 2024-02-06 4:00:47 PM
2024-02-06 16:00:47.7356 TRACE: [dje_z9U8QJS9HFVVKEZ7U8D9Q3S2FN9UQ_ejd][MoveNext] : Cluster ranking search: DXCC 318 China -> 282
2024-02-06 16:00:49.4666 TRACE: [dje_zAJS4KJ28ZPBPGB6ZJVWNQ_ejd][MoveNext] : Executing planned scheduler...

[IW3HMH]

Thanks, checking the issue

[w9mdb]

Just tested 2.3.1.08 and alert on band is still broken.
Didn't see any fix for it in the release notes and I kind of thought this would be a priority.

[IW3HMH]

Hi Mike, i just did that:

Set the alert to spot "non confirmed bands" in the last tab, confirmation type set to "QSL" (only QSL selected in the list) (i don't have any confirmation on 80m for china in test database).
No other settings on that.

Started a localhost cluster server from log4om and connected log4om cluster to this one (to avoid having noise due to real incoming spots). now log4om is connected to his own cluster server that is not receiving any spot from outside so i don't have any other cluster spot during tests.

1) Added a spot simulation to BA5CJ on 80m CW. Alert triggered correctly

2) Added BA5CJ to log and sent a new spot to BA5CJ on 80m CW. The spot WAS NOT ALERTED as it was PREVIOUSLY SPOTTED in the same session and log4om doesn't send duplicate alerts (there is a time range). The alert is not sent due to "duplicate prevention" not because it has been WORKED (we requested the non CONFIRMED bands so this qso is not confirmed by definition), if you close log4om with BA5CJ on the log, unconfirmed, on new start it will be notified again...

3) Added a spot to BA5DX on 80M cw and log4om correctly alerted it...

So according to my tests everything is working as expected...

[w9mdb]

What's not working now is the email notification....not getting one.

Just had another spot where I had 20M confirmed but the spot was on 10M and got the audio alert -- but no email.

[KI5IO]

What's not working now is the email notification....not getting one.

Just had another spot where I had 20M confirmed but the spot was on 10M and got the audio alert -- but no email.

Mike,

I just did a spot simulation test (after I enabled the e-mail alert as I don't often use) and it worked FB for my test.

Simple simulation on 40m CW.

[w9mdb]

BA5DX is worked 80M but not confirmed.
BA5CJ is worked only on 40M confirmed.
6M has nothing worked
80M has a worked which is BA5DX -- not BA5CJ so not worked B4 on 80M but was worked on 40M.
Here is a 6M spot which does give the audio alert and the email. 80M spot debug below.

[Simulation] DX de WA1SXK: 50313.0 BA5CJ FT8 1416Z
2024-03-12 14:16:39.0307 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : Performing QSO search on callsign BA5CJ
2024-03-12 14:16:39.0347 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call BA5CJ on date 2024-03-12 2:16:39 PM
2024-03-12 14:16:39.0447 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : No Clublog CQ ZONE found for BA5CJ
2024-03-12 14:16:39.0506 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : Searching clublog exceptions
2024-03-12 14:16:39.0526 TRACE: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : No Clublog exceptions found for BA5CJ
2024-03-12 14:16:39.0526 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : LOTW user identified
2024-03-12 14:16:39.0536 DEBUG: * [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext][22 ms] : QSO search on callsign BA5CJ completed
2024-03-12 14:16:39.0546 DEBUG: * [Countries][SearchCallsign][19 ms] : Performing Search Callsign on call BA5CJ on date 2024-03-12 2:16:39 PM
2024-03-12 14:16:39.0646 TRACE: [ProgramStorage][GetFlag] : Flag CHN identified.
2024-03-12 14:16:39.0666 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call WA1SXK on date 2024-03-12 2:16:39 PM
2024-03-12 14:16:39.0776 DEBUG: [dje_z7JFPYWMUBVHCYV49Y9D59LS7W7VA_ejd][MoveNext] : SPOT mode overriden to FT8
DX de WA1SXK: 50313.0 BA5CJ FT8 1416Z
2024-03-12 14:16:39.0905 TRACE: [dje_z7JFPYWMUBVHCYV49Y9D59LS7W7VA_ejd][MoveNext] : Cluster ranking search: DXCC 318 China -> 282
2024-03-12 14:16:39.2291 INFO: [dje_zCQZL8WCJCWP97A92THPR2_ejd] : [CLUSTER ALERT] Sending e-mail
2024-03-12 14:16:39.2320 INFO: [dje_zEBJFEP55F5FGFM8AUH5JSB9R49VQ_ejd] : Sending e-mail to 8023381851@vzwpix.com
2024-03-12 14:16:43.9950 TRACE: [dje_zUGSCJ5V5X3RPAY84WDGFS_ejd][MoveNext] : Executing planned scheduler...

And now the 80M spot which does not trigger audio or email -- it's missing the CLUSTERALERT line....
[Simulation] DX de WA1SXK: 3053.0 BA5CJ FT8 1417Z
2024-03-12 14:17:35.0450 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : Performing QSO search on callsign BA5CJ
2024-03-12 14:17:35.0490 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call BA5CJ on date 2024-03-12 2:17:35 PM
2024-03-12 14:17:35.0600 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : No Clublog CQ ZONE found for BA5CJ
2024-03-12 14:17:35.0660 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : Searching clublog exceptions
2024-03-12 14:17:35.0680 TRACE: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : No Clublog exceptions found for BA5CJ
2024-03-12 14:17:35.0680 DEBUG: [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext] : LOTW user identified
2024-03-12 14:17:35.0690 DEBUG: * [dje_zKZZWQMU795TF58DYVVJLGFUJPHKK4RDPVS_ejd][MoveNext][23 ms] : QSO search on callsign BA5CJ completed
2024-03-12 14:17:35.0690 DEBUG: * [Countries][SearchCallsign][19 ms] : Performing Search Callsign on call BA5CJ on date 2024-03-12 2:17:35 PM
2024-03-12 14:17:35.0789 TRACE: [ProgramStorage][GetFlag] : Flag CHN identified.
2024-03-12 14:17:35.0809 DEBUG: [Countries][SearchCallsign] : Performing Search Callsign on call WA1SXK on date 2024-03-12 2:17:35 PM
2024-03-12 14:17:35.0929 DEBUG: [dje_z7JFPYWMUBVHCYV49Y9D59LS7W7VA_ejd][MoveNext] : SPOT mode overriden to FT8
DX de WA1SXK: 3053.0 BA5CJ FT8 1417Z
2024-03-12 14:17:35.1068 TRACE: [dje_z7JFPYWMUBVHCYV49Y9D59LS7W7VA_ejd][MoveNext] : Cluster ranking search: DXCC 318 China -> 282
2024-03-12 14:17:35.1383 TRACE: [dje_zUGSCJ5V5X3RPAY84WDGFS_ejd][MoveNext] : Executing planned scheduler...
2024-03-12 14:17:35.1383 TRACE: [LogWriter][DumpProcess] : ## DUMP MODULES ##
2024-03-12 14:17:35.1393 TRACE: [LogWriter][DumpProcess] : ## DUMP ##SearchCallsign Countries 1
2024-03-12 14:17:35.1403 TRACE: [dje_zNQN2PU7B_ejd][dje_z3Y7A6PDYKQMBUAWJNBLQF8FSJZFHU3E2C2_ejd] : ################# START Update solar image from scheduler
2024-03-12 14:17:35.1403 TRACE: [MapManagement][MakeSunImage] : Painting sun image...
2024-03-12 14:17:35.7949 TRACE: [MapManagement][CreateBitmapWithPosition] : Creating bitmap with station position

Screenshot 2024-03-12 092956.png (54.76 KiB) Viewed 1215 times

Screenshot 2024-03-12 093405.png (20.57 KiB) Viewed 1215 times

[IW3HMH]

i will add some more trace log rows...
something was not triggered, but can't assume it's an error at this time with current info

[IW3HMH]

just to make something clear:
the alert is NOT reporting/checking if a single callsign is worked or not (except for specific rules involving specific calls). It works by DXCC for the function you selected, so callsign is not relevant.
if an alert has been triggered the alert will not be triggered again. Here the callsign is relevant, as the "non flooding" function works by call also.

I'm about to release a new alpha version with some more log traces.

[w9mdb]

Tested with 2.31.1.0
ZA/IW2JOP is validated on 10M/12M
ZA5G is worked on 15M
I do spot on ZA/IW2JOP on 15M and no alert

Screenshot 2024-03-16 083805.png (27.59 KiB) Viewed 1066 times

Do another spot on 14074 and I get the alerts.
Here's my log so you can duplicate this
https://www.dropbox.com/scl/fi/4eek3p39 ... 2oqm3&dl=0
Is is possible it's doing "unworked on band" instead of "not confirmed" or that the "not confirmed" logic is using the wrong status?
Debug log shows
2024-03-16 13:33:45.1486 TRACE: [dje_zXAMEFFTNE228EVM2EGF2F_ejd][MoveNext] : [CLUSTER ALERT] Parsing incoming spot: DX de W9MDB: 21091.0 ZA/IW2JOP FT8 1333Z
2024-03-16 13:33:45.1486 TRACE: [FwHam][ExtractCallsign] : Extracting callsign from NC7L
2024-03-16 13:33:45.1496 TRACE: [FwHam][ExtractCallsign] : NC7L -> NC7L with prefix
2024-03-16 13:33:45.1496 TRACE: [FwHam][ExtractCallsign] : Extracting callsign from NC7L
2024-03-16 13:33:45.1496 TRACE: [FwHam][ExtractCallsign] : NC7L -> NC7L with prefix
2024-03-16 13:33:45.1512 TRACE: [FwHam][ExtractCallsign] : Extracting callsign from NC7L
2024-03-16 13:33:45.1512 TRACE: [FwHam][ExtractCallsign] : NC7L -> NC7L with prefix
2024-03-16 13:33:45.1512 TRACE: [FwHam][ExtractCallsign] : Extracting callsign from NC7L
2024-03-16 13:33:45.1522 TRACE: [FwHam][ExtractCallsign] : NC7L -> NC7L with prefix
2024-03-16 13:33:45.1522 TRACE: [FwHam][ExtractCallsign] : Extracting callsign from NC7L
2024-03-16 13:33:45.1522 TRACE: [FwHam][ExtractCallsign] : NC7L -> NC7L with prefix
2024-03-16 13:33:45.1532 TRACE: [FwHam][ExtractCallsign] : Extracting callsign from NC7L
2024-03-16 13:33:45.1532 TRACE: [FwHam][ExtractCallsign] : NC7L -> NC7L with prefix
2024-03-16 13:33:45.1512 TRACE: [dje_zXAMEFFTNE228EVM2EGF2F_ejd][MoveNext] : [CLUSTER ALERT] Spot doesn't match current rule: (DXCC) DX de W9MDB: 21091.0 ZA/IW2JOP FT8 1333Z