For anyone else that may come across this post, support was not able to determine the root cause of the issue, but we were able to get it resolved for at least the time being. The fix was to stop the gateway, delete the alarms cache (on linux it is a hidden file in the ‘var/lib/ignition/data’ folder called “.alarms_”), and start the gateway. We are keeping an eye on things to see if starts happening again.