Alarm on BACnet tag goes active but never enters the notification pipeline (memory tag alarm works)

Hi everyone,

I'm new to Ignition and building an alarm board, and I'd appreciate help with a notification issue.

Setup

  • Ignition 8.1 (trial), Perspective alarm status table
  • Alarm notification pipeline: Splitter → Notification block (email, on-call roster) → Delay → Expression (isAcknowledged) → Script (phone call)
  • Second Splitter output → Notification block emailing a second roster

What works

  • A memory tag (simulated temperature) with an Above Setpoint alarm sends the email correctly through this pipeline.

What doesn't work

  • A BACnet/IP tag (live value from a Niagara JACE, through the Ignition OPC UA server) with an alarm set up the same way goes Active, Unacknowledged on the alarm status table, but no email is sent and nothing appears in the gateway logs.

What I've checked

  • Both alarms use the same Active Pipeline: samplequickstart/management_pipeline
  • Ack Mode is Manual; the alarm is left unacknowledged for 2+ minutes
  • Email profile test works, and the From Address issue (SendAsDenied) is fixed
  • Alarm Notification module is running, and the project is enabled
  • Both rosters have a user with an email address

The only differences in the tag JSON

  • The BACnet tag is readOnly: true
  • Its alarm has empty custom properties left over from earlier (CustomEmailSubject: "", CustomEmailMessage: "", voip.customMessage: ""), plus empty ackPipeline and clearPipeline

Could the empty custom message properties stop the notification, or is there something else that would keep an alarm on an OPC tag from entering the pipeline?

Thank you!