# \[Ignition 8.0.7\] Active pipeline not triggered for the first time each alarm occur **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [January 15, 2020, 5:34pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304 "2020-01-15T17:34:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [January 15, 2020, 5:34pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/1 "2020-01-15T17:34:14Z")
I have an application upgraded from 7.9.13. When I restart Ignition, I have an alarm pipeline associated for the active state for multiple tag alarms. When each alarm became **active** , the first active state of each alarm doesn’t trigger the pipeline. The second one is ok. **I suspect that the initial active state is filtered ?** In 7.9.13 I don’t have this behavior. @Paul.Scott Is there ever a bug reported for this ? ---
**Author:** ![Paul.Scott](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul.scott/32/4578_2.png) [@Paul.Scott](https://forum.inductiveautomation.com/u/Paul.Scott)\ **Post date:** [January 28, 2020, 8:44pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/2 "2020-01-28T20:44:54Z")
Thanks for the report! Sorry about the delay: the post came right as I started vacation. > [@mazeyrat](#): > > Is there ever a bug reported for this ? Not that I can see. I know this was a while ago, but any other details? Notable errors in the gateway? I can try to have some folks replicate internally, but any other details you may have are appreciated. ---
**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\ **Post date:** [January 28, 2020, 11:45pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/3 "2020-01-28T23:45:27Z")
I’m pretty confident what’s occurring here is expected. I have also confirmed the behavior is the same in 7.9.13 as it is in 8.0.8. The first subscribed tag value after startup is considered an initial event, which by default doesn’t enter the notification system. These events will result in notifications _if_ “notify initial events” is enabled _and_ the minutes passed since shutdown exceeds the “continuous event detection window.” New active, unacknowledged events won’t be generated if this detection window hasn’t been exceeded, since the original alarm event prior to shutdown will be retained, hence why a notification isn’t sent. So to summarize, if these alarms are active on shutdown, and then the Gateway is restarted within the event detection window, it is expected (with default settings) that, on startup, the _prior_ event is loaded, and thus no new event occurs, hence why no notification is sent. If the Gateway is restarted outside the event detection window, _new_ events will be generated for these alarms, but won’t enter its pipeline if notify initial events is false. If the alarms _weren’t_ active on shutdown, then new events would be generated on startup (being that now active) and, similar to before, would only enter its pipeline if notify initial events is true. If you’re wanting new active events to be generated always on startup and for initial alarm events to enter their respective pipelines, then it would be best to set the detection window to 0 and notify initial events to true. Both of these Gateway settings are under the Event Suppression category in Alarming -\> General. ---
**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\ **Post date:** [January 29, 2020, 3:30pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/4 "2020-01-29T15:30:01Z")
Thanks a lot for these clarifications. Notify initial events was set to False in v8. I will test again ---
**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\ **Post date:** [January 29, 2020, 5:45pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/5 "2020-01-29T17:45:51Z")
Kurt, what is the largest number that can be placed in the continuous event detection window? ---
**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\ **Post date:** [January 30, 2020, 4:28pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/6 "2020-01-30T16:28:03Z")
This is equal to Java’s Integer.MAX\_VALUE, which is 2147483647. 2,147,483,647 minutes would equal to about ~4,086 years.