Alarm priority binding bug?

I have a UDT with OPC tags.
One is Priority (integer),
One is AlarmStat (bool).

The AlarmStat tag has an alarm configured on it, with the priority bound to the Priority tag.

If I navigate into the tag tree and drill down to the Alarms/Alarm/Priority - many of my instances show null, even though my Priority tag has a valid value.

If I restart the UDT, it evaluates the binding properly and shows a valid value.
If I simply change the value of the Priority tag, it does NOT fix it.

Anyone else seen this? What's the cause? It's as if the binding isn't being properly setup?

Do you have screenshots of how the UDT and tags are set up? I could be misunderstanding.

I tested it with some memory tags and it seemed to work and update if I had the Priority tag set up as the binding on the alarm priority or if I created a Priority parameter and linked the alarm's priority to the parameter.

It did say null until I triggered the alarm for the first time before switching to the priority level I had the Priority tag set at between 0-4. It also would not update to the new priority when I changed the value on the Priority tag unless the alarm value was triggered on or off. So maybe the tags you had showing null were alarms that hadn't updated or been triggered since being created?