# Broken Custom Alarm Notifications after Upgrade to 8.1.2

**URL:** <https://forum.inductiveautomation.com/t/broken-custom-alarm-notifications-after-upgrade-to-8-1-2/45507>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 12, 2021, 7:54pm UTC](https://forum.inductiveautomation.com/t/broken-custom-alarm-notifications-after-upgrade-to-8-1-2/45507 "2021-04-12T19:54:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![AIO](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/aio/32/87549_2.png) [@AIO](https://forum.inductiveautomation.com/u/AIO)\
**Post date:** [April 13, 2021, 12:03am UTC](https://forum.inductiveautomation.com/t/broken-custom-alarm-notifications-after-upgrade-to-8-1-2/45507/2 "2021-04-13T00:03:35Z")

</div>

After speaking with support, it sounds like in order for the following syntax to work, it needs to be forced into an expression.

```auto
At {eventTime|hh:mm:ss}, alarm "{name}" at "{displayPath}" transitioned to {eventState}.

```

Would then become:

```auto
'At '+"{eventTime|hh:mm:ss}"+', alarm '+"{name}"+' at '+"{displayPath}"+' transitioned to '+"{eventState}"+'. '

```

Once done, the issue with the tag references appears to have resolved itself.  
Definitely an issue to be aware of when upgrading from 7.9 to 8.1.2.

---

_[View the full topic](https://forum.inductiveautomation.com/t/broken-custom-alarm-notifications-after-upgrade-to-8-1-2/45507)._