# Forcing Immediate Alarm Evaluation **URL:** \ **Category:** Ignition\ **Created:** [September 2, 2020, 9:00pm UTC](https://forum.inductiveautomation.com/t/forcing-immediate-alarm-evaluation/38329 "2020-09-02T21:00:50Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\ **Post date:** [September 2, 2020, 9:00pm UTC](https://forum.inductiveautomation.com/t/forcing-immediate-alarm-evaluation/38329/1 "2020-09-02T21:00:50Z")
After reading up some excellent hints on how “Notify Initial Events” works from [here](http://forum.inductiveautomation.com/t/ignition-8-0-7-active-pipeline-not-triggered-for-the-first-time-each-alarm-occur/31304/3) and [here](http://forum.inductiveautomation.com/t/email-notification-on-tag-not-working/23911/3), I think I would like very much to be able to force the immediate alarm evaluation of a slow/digital tag. I’m having an issue where I set up an alarm on a tag that rarely updates (hours or longer), and that first change _should_ be an alarm event but is skipped because it is considered the “initial event”. I’m assuming the alarm evaluation is triggered by a tag changing value, but I can’t force these tags to update their value on-demand. It’s remotely controlled and only on-change. Does anyone know another way to force an alarm evaluation immediately? I basically just want the value at the moment the alarm is enabled be considered as the “initial event”? ---
**Author:** ![diat150](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@diat150](https://forum.inductiveautomation.com/u/diat150)\ **Post date:** [September 3, 2020, 2:40am UTC](https://forum.inductiveautomation.com/t/forcing-immediate-alarm-evaluation/38329/2 "2020-09-03T02:40:13Z")
all you can really do is set the notify initial event property.