# Are invalid alarm notification pipelines defined in tags displayed as errors anywhere?

**URL:** <https://forum.inductiveautomation.com/t/are-invalid-alarm-notification-pipelines-defined-in-tags-displayed-as-errors-anywhere/65580>\
**Category:** Ignition\
**Created:** [October 24, 2022, 3:52am UTC](https://forum.inductiveautomation.com/t/are-invalid-alarm-notification-pipelines-defined-in-tags-displayed-as-errors-anywhere/65580 "2022-10-24T03:52:30Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [October 24, 2022, 3:52am UTC](https://forum.inductiveautomation.com/t/are-invalid-alarm-notification-pipelines-defined-in-tags-displayed-as-errors-anywhere/65580/1 "2022-10-24T03:52:30Z")

</div>

I've intentionally added a bogus prefix to some tag alarm notification profile names on some select tags that a site doesn't want paged out temporarily. When I tested it, the alarms didn't page out, but I also didn't see any errors produced in the logs which I was expecting to see. Wanted to see what the go is here?

---

<div class="post-metadata">

**Author:** ![obober](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/obober/32/67865_2.png) [@obober](https://forum.inductiveautomation.com/u/obober)\
**Post date:** [October 24, 2022, 10:09pm UTC](https://forum.inductiveautomation.com/t/are-invalid-alarm-notification-pipelines-defined-in-tags-displayed-as-errors-anywhere/65580/2 "2022-10-24T22:09:15Z")

</div>

Why use a prefix in front of the pipeline name? Why not just disable the alarm pipeline in the Pipeline Block Editor? If you disable it there, you get a warning saying that it's disabled:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/6/6600b49c582bcefa5684575b41bac4916d76ffb6.png)

---

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [October 24, 2022, 10:45pm UTC](https://forum.inductiveautomation.com/t/are-invalid-alarm-notification-pipelines-defined-in-tags-displayed-as-errors-anywhere/65580/3 "2022-10-24T22:45:02Z")

</div>

Do you mean inside of the alarm pipeline definition itself? If so, I have a number of other alarms that also use this pipeline that I want to keep paging alarms out, it's only a select few that they want temporarily disabled. The reason I renamed with a prefix was so that I had something to find/replace when I need to re-enable paging for them again.

---

<div class="post-metadata">

**Author:** ![obober](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/obober/32/67865_2.png) [@obober](https://forum.inductiveautomation.com/u/obober)\
**Post date:** [October 24, 2022, 11:14pm UTC](https://forum.inductiveautomation.com/t/are-invalid-alarm-notification-pipelines-defined-in-tags-displayed-as-errors-anywhere/65580/4 "2022-10-24T23:14:55Z")

</div>

Ah, I see what you mean now, I misunderstood your original post.

If you set the `Notification.PipelineManager` logger to DEBUG, you can see this in the logs:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/1/d1d2010944742e14e602dea1a7dfa0e46274f9af.png)