# Lost Alarm Properties (Active Pipeline)

**URL:** <https://forum.inductiveautomation.com/t/lost-alarm-properties-active-pipeline/12762>\
**Category:** Ignition\
**Created:** [March 8, 2017, 1:43am UTC](https://forum.inductiveautomation.com/t/lost-alarm-properties-active-pipeline/12762 "2017-03-08T01:43:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![djseverson](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@djseverson](https://forum.inductiveautomation.com/u/djseverson)\
**Post date:** [March 8, 2017, 1:43am UTC](https://forum.inductiveautomation.com/t/lost-alarm-properties-active-pipeline/12762/1 "2017-03-08T01:43:32Z")

</div>

I am using a script (in Ignition 7.9) to allow users to update the alarm priority of a tag using  
system.tag.editAlarmConfig(tagpath,almConfig)

Here is a sample print of the parameters:  
[u’Waste/MCP/BIOLAC/BIOLAC\_GATE\_FAIL’] {u’alarm’: [[‘priority’, ‘Value’, 3]]}

Executing this script causes my Active Pipeline entry (and some other alarm parameters) to be lost. Subsequent attempts to restore the pipeline from within the tag editor are not accepted. Modifications to the alarm properties do not take after executing the script. The only way I can recover control of the alarm parameters for a script modified tag is to reload my tag export (made prior to updating the alarm by script). Other tags not modified by script continue to function normally.

Following is a sample comparison of a tag from the XML Tag dump before and after executing the script.

**AFTER\_SCRIPT\_EXECUTION**  
  
false  
6  
ignition

```
     </Alarm>
  </Alarms>

```

**BEFORE\_SCRIPT\_EXECUTION**  
  
false  
6  
ignition  
  
  
Test Alarm Note  
First Step/WWTP  
Test Alarm Display Path  
3

---

<div class="post-metadata">

**Author:** ![adam.morales](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/adam.morales/32/3405_2.png) [@adam.morales](https://forum.inductiveautomation.com/u/adam.morales)\
**Post date:** [March 9, 2017, 12:07am UTC](https://forum.inductiveautomation.com/t/lost-alarm-properties-active-pipeline/12762/2 "2017-03-09T00:07:26Z")

</div>

Is this alarm part of a UDT member tag? This could have to do with the fact that you cannot override individual alarm properties, only redefine the entire alarm. If so, then the only workaround for this right now is to create another member tag which holds the value, and bind the property to this tag.

---

<div class="post-metadata">

**Author:** ![djseverson](https://avatars.discourse-cdn.com/v4/letter/d/ecae2f/32.png) [@djseverson](https://forum.inductiveautomation.com/u/djseverson)\
**Post date:** [March 9, 2017, 12:40am UTC](https://forum.inductiveautomation.com/t/lost-alarm-properties-active-pipeline/12762/3 "2017-03-09T00:40:17Z")

</div>

Not a UDT. The behavior is occurring with any alarm tag in my external . The code behaved properly on another application in version 7.8. This 7.9 application was upgraded and modified from 7.6. Maybe it is related to alarm subsystem modifications from 7.7 to 7.8. I will create a stripped down project and see if I can replicate the behavior: 1.) with my existing tag provider and 2.) with a new tag provider.