Error calling reference paths in Alarm Display Path expression

Hello,

I am currently using Ignition 8.3.x in a Linux (Docker) environment.

I am experiencing an issue where an Alarm's Display Path is configured with an Expression that references Memory Tag values. When the Gateway is restarted while alarms are active, the values of the referenced tags are omitted from the Display Path when the active alarm tags are reloaded.

I tested this by manually triggering around 60 alarms using Memory Tags. The alarms with omitted values display properly once they are cleared and re-triggered (toggled from False to True). Additionally, for the first few seconds after a restart, the alarms are sequentially loaded with the referenced values omitted before subsequent alarms begin displaying normally.

Since the Display Path itself does not dynamically re-compile/re-evaluate once triggered, I suspect this issue occurs because the alarms are called during Gateway startup before the referenced tag values have fully loaded into memory.

I am wondering if anyone else has experienced this same behavior.

Below are the expressions used, and the tags being omitted are {[.]../DeviceLocation} and {[.]../DeviceName}:

  1. {[.]../DeviceLocation} + " " + {[.]../DeviceName} + " " + {TagName} + " - " + "[Tag : " + {PathToParentFolder} + "/" + {TagName} + "]"
  2. concat({[.]../DeviceLocation}, " ", {[.]../DeviceName}, " ", {TagName}, " - [Tag : ", {PathToParentFolder}, "/", {TagName}, "]")

Unlike expression tags, where the expression makes a subscription to any nested tags, expressions in tag property bindings do not subscribe. For most tag properties, the binding is only evaluated at tag initialization or re-initialization, such as when UDT parameters are changed. For alarm properties, the expressions are evaluated at tag init and thereafter on tag events. Tag events that fire when the nested tags are not yet populated will snapshot that empty value.

This is a pretty fundamental Ignition architecture item--only expression tags themselves are fully hooked into values from other tags. You should consider an approach where those alarm display paths are constants, and write to them from tag events attached to the DeviceLocation and DeviceName tags. (But only if the new display path is different, to avoid unnecessary tag re-initializations.)