# Odd Notification Pipeline Behavior

**URL:** <https://forum.inductiveautomation.com/t/odd-notification-pipeline-behavior/101737>\
**Category:** Ignition\
**Created:** [February 2, 2025, 9:22pm UTC](https://forum.inductiveautomation.com/t/odd-notification-pipeline-behavior/101737 "2025-02-02T21:22:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Eric\_Keen](https://avatars.discourse-cdn.com/v4/letter/e/e68b1a/32.png) [@Eric\_Keen](https://forum.inductiveautomation.com/u/Eric_Keen)\
**Post date:** [February 2, 2025, 9:22pm UTC](https://forum.inductiveautomation.com/t/odd-notification-pipeline-behavior/101737/1 "2025-02-02T21:22:57Z")

</div>

I have set up a simple alarm on a tag to send an email notification when the tag value is zero. I have an active delay of 5 seconds.

- The notification test email through the Gateway works properly.
- The alarm triggers properly when the tag is set to 0.
- The pipeline is selected for the active pipeline in the alarm settings.

Despite this, the alarm rolling to "Active" will not send the email. I believe it is not triggering the pipeline at all as I have added a logger script in the pipeline and do not see any of the logs in the logger.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 3, 2025, 4:40pm UTC](https://forum.inductiveautomation.com/t/odd-notification-pipeline-behavior/101737/2 "2025-02-03T16:40:55Z")

</div>

How are you testing? Are you directly writing a value to the tag, or are you opening the tag editor to supply a new value?

---

<div class="post-metadata">

**Author:** ![Eric\_Keen](https://avatars.discourse-cdn.com/v4/letter/e/e68b1a/32.png) [@Eric\_Keen](https://forum.inductiveautomation.com/u/Eric_Keen)\
**Post date:** [February 4, 2025, 8:19pm UTC](https://forum.inductiveautomation.com/t/odd-notification-pipeline-behavior/101737/3 "2025-02-04T20:19:48Z")

</div>

So it turns out that the "Notify Initial Events" selection in the Gateway settings under Alarming -\> General fixed this issue.