# Alarm and transaction group on same tag

**URL:** <https://forum.inductiveautomation.com/t/alarm-and-transaction-group-on-same-tag/21200>\
**Category:** Ignition\
**Created:** [December 3, 2018, 5:31pm UTC](https://forum.inductiveautomation.com/t/alarm-and-transaction-group-on-same-tag/21200 "2018-12-03T17:31:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\
**Post date:** [December 3, 2018, 5:31pm UTC](https://forum.inductiveautomation.com/t/alarm-and-transaction-group-on-same-tag/21200/1 "2018-12-03T17:31:05Z")

</div>

Good Morning,

I have an issue that appears to have started after I created a transaction group for a tag. The tag was already an alarm with a working alarm pipeline that sent out email notifications to the on-call roster. However, this functionality died upon also writing a transaction group with the same tag. Has anyone had this issue before where an email alarm notification pipeline that previously worked, does not work upon adding the alarm to a separate transaction group?

Thanks!

---

<div class="post-metadata">

**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\
**Post date:** [December 3, 2018, 5:34pm UTC](https://forum.inductiveautomation.com/t/alarm-and-transaction-group-on-same-tag/21200/2 "2018-12-03T17:34:50Z")

</div>

Nevermind, I renamed the pipeline, but didn’t change the pipeline in the tag configuration. Sorry!