When I use binding in a Custom Message, the message that is sent reverts back to the default defined by the Notification block.
This does not occur when the Custom Message does not use binding.
You’re talking about the Custom Message field configured on an Alarm, right?
Yes, the alarm associated with the tag
Yeah, I can reproduce this… thanks for the report. I’ll fix it for 7.6.3.
I take it back, this does work. You probably just don’t have a valid expression configured. There should be something logged to the console on the gateway to this effect when you edit/save the alarm. When this happens, the pipeline ends up acting as if the custom message isn’t defined.
You also need to make sure the Message Mode is Custom:
