# Trigger conditions not being observed
**URL:** https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476
**Category:** Support
**Tags:** done
**Created:** [September 10, 2026, 12:19am UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476 "2026-09-10T00:19:35Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@N6NXV](https://forum.hamalert.org/u/N6NXV)
#### Post date: [September 10, 2026, 12:19am UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/1 "2026-09-10T00:19:35Z")
I have several triggers setup with “Spotter state” set to _ **only** _ California, but I get spots from stations the east coast anyway. These stations all show NY, PA, FL, etc when I check their location on [QRZ.com](http://QRZ.com)
The only way to kill those notifications is to add the spotter call to the “not Spotter callsign” list. “California only” isn’t filtering them out.
This seems to have begun recently.
Has something changed that I need to fix.
---
### Author:  [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)
#### Post date: [September 10, 2026, 6:14am UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/2 "2026-09-10T06:14:14Z")
Could you post a screenshot of an errant spot, with the spot details opened, please? That would help me troubleshoot the issue.
---
### Author:  [@N6NXV](https://forum.hamalert.org/u/N6NXV)
#### Post date: [September 10, 2026, 6:09pm UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/3 "2026-09-10T18:09:42Z")
Here are two screenshots of “non California” spotters
---
### Author:  [@N6PE](https://forum.hamalert.org/u/N6PE)
#### Post date: [September 10, 2026, 10:39pm UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/4 "2026-09-10T22:39:50Z")
Is the reverse true also, I.E. if W0PE in CA spots something do you get it?
---
### Author:  [@N6NXV](https://forum.hamalert.org/u/N6NXV)
#### Post date: [September 10, 2026, 11:29pm UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/5 "2026-09-10T23:29:34Z")
Yes, the trigger has been “call sign agnostic”. It doesn’t seem to matter what zone is in the spotter’s call.
California is a big state and I’ve had to “Not Spotter callsign” quite a few spotters that are FAR from me, but still in CA. That list has all zones represented.
---
### Author:  [@HB9DQM](https://forum.hamalert.org/u/HB9DQM)
#### Post date: [September 12, 2026, 4:20pm UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/6 "2026-09-12T16:20:32Z")
Aha! I found the reason. The callsign info file that HamAlert downloads from the FCC once a week may contain multiple records for the same callsign, and the latest record/owner may not be the last one in the file. So I had to modify the import script to check for the highest Unique System Identifier to import the newest record rather than a potentially superseded assignment.
So this should now be fixed. Thanks for the report!
---
### Author:  [@N6NXV](https://forum.hamalert.org/u/N6NXV)
#### Post date: [September 12, 2026, 6:10pm UTC](https://forum.hamalert.org/t/trigger-conditions-not-being-observed/2476/7 "2026-09-12T18:10:05Z")
Great tool and great support.
Thank you