Alarm Metrics UDT aggregation

Ignition
1

Hello everyone,

I am working with Ignition 8.3.3 and I’m having some trouble understanding the new Alarm Metrics behavior with nested UDTs.

My setup:

  • I have a base UDT (e.g., "Digital_In") that contains an alarm.
  • This base UDT is nested inside a parent UDT (e.g., "Motor").
  • I am using multiple levels of UDT inheritance/nesting.

The issue: When an alarm is active in the child UDT ("Digital_In"), the alarm count or status is visible within that child instance, but it doesn't seem to propagate or aggregate up to the parent UDT's alarm metrics automatically.

Questions:

  1. Is there a specific property I need to enable in the parent UDT to aggregate the alarm metrics from its nested children?
  2. Does the deep nesting (UDT within UDT) affect how these metrics are calculated or updated?

Any guidance on the correct workflow for 8.3.3 Alarm Metrics in complex UDT structures would be greatly appreciated!

Thanks in advance.

2

Additional context:

What’s even more confusing is that I have a similar setup (UDT nested inside another UDT) where the alarm metrics are working correctly and propagating to the parent. However, for my "Digital" and "Analog" base UDTs, the count stays at zero in the parent even when the child has active alarms.

I have compared both structures and they look identical. I’ve also searched for an "Enable Aggregation" toggle in the Tag Editor (under Alarming or Alarm Metrics), but I cannot find a specific property to turn this on or off manually.

It seems inconsistent—some nested UDTs aggregate while others don't, despite having the same configuration. Has anyone else noticed this behavior in version 8.3.3? Could this be related to how deep the nesting goes or a specific tag property that I'm overlooking?

3

Update: I found the root cause but not a direct UI fix. It seems like a bug when copy-pasting elements inside a UDT definition in 8.3.3.

When I copy-paste a tag or a nested UDT, it creates "ghost overrides" that cannot be cleared in the UI. These corrupted references prevent Alarm Metrics from aggregating to the parent. However, if I create the exact same structure manually (element by element) without copying, the metrics aggregate perfectly.

Is there a way to "deep clean" these internal overrides without rebuilding the entire UDT from scratch?

I am not sure if this is a specific issue with my Gateway installation or a general bug in version 8.3.3. However, the behavior is consistent: copy-pasting objects within a UDT definition results in broken Alarm Metrics, while manual creation works fine. Has anyone else encountered this 'ghost override' behavior in this version, or could it be related to a corrupted local cache/installation?

4

I would export those UDTs and compare the 2 to see what you can find different between them.