Are you using SQLTags located in an external DB? I have had problems in the past with what I’ve termed to tech support as “orphaned” alarms when I’ve changed an alarm name or setting after it has already alerted and been left unable to ack or clear them. Real pain in the butt that I’ve only been able to resolve by unchecking the “apply alarms across restarts” setting under the gateway config, then restarting the gateway. Would love to hear a better solution!