Advanced Alert Priority when incident matches multiple alerts

In theory both alerts should fire. For the test node in question, is the "Comments" field populated? If blank, we may not like the NULLs when evaluating the "is not equal to" clause.

The comments field is populated

and ExcludeRebootAlerts?

That is a good catch. It was set to “None” instead of No or Yes. I am trying to find a location that will let me set the default to no for every new node added, but I can’t seem to find a way to do that without recreating the custom property. Does anyone know how to make that change?

in the database editor something like:

ALTER TABLE nodes
ADD CONSTRAINT def_property DEFAULT 'No' FOR property

[untested]

Thanks. I deleted it and recreated it earlier.