# \[BUG-13866\] Expression isAlarmActive : Invalid relative tag path **URL:** \ **Category:** Ignition Early Access\ **Tags:** ignition80\ **Created:** [June 4, 2019, 1:47pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536 "2019-06-04T13:47:52Z")\ **Posts on this page:** 19\ **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:** [June 4, 2019, 1:47pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/1 "2019-06-04T13:47:52Z")
@awalker, can you fill a ticket for this: **Ignition 8.0.2-rc1** Note : the same UDT and expression work fine in Ignition 7.9.10. Error for an expression tag inside an UDT with **isAlarmActive("[.]…/TM/ETAT\_ALIM\_1")** ```auto Quality Diagnostics Invalid relative tag path '[.]../TM/ETAT_ALIM_1'. No enclosing tag could be found. WARN ``` ![xml%20-%20TVG-GTC02](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/30a49f733e94aff4c16da141b2332af8a62dff65.png) ---
**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\ **Post date:** [June 4, 2019, 8:34pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/2 "2019-06-04T20:34:57Z")
Hi @mazeyrat, I had someone look at this and it looks the same as an issue we are tracking already. I’ve linked the ticket number above and will let you know when its been fixed. ---
**Author:** ![awalker](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/awalker/32/6874_2.png) [@awalker](https://forum.inductiveautomation.com/u/awalker)\ **Post date:** [July 23, 2019, 3:45pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/3 "2019-07-23T15:45:35Z")
This issue was fixed in the 8.0.4 Nightly build that was uploaded today (7/23). ---
**Author:** ![apgilber](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@apgilber](https://forum.inductiveautomation.com/u/apgilber)\ **Post date:** [August 9, 2019, 1:14pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/4 "2019-08-09T13:14:24Z")
Was there a nightly released since July 18th with this fix? I seem to be having the same error on the isAlarmActiveFiltered using a wildcard for the tag path and we downloaded a nightly on August 1st. What’s weird is the website says the last nightly was July 18th but our modules show August 1st. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d27cc842b5d50950b616a869e04d54cfaa3a119f.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/7316f194e2a8adee58abebfce23e6cc75d1de965.png) ---
**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:** [August 9, 2019, 3:03pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/5 "2019-08-09T15:03:09Z")
The “release date” on our website is inaccurate, for a variety of technical reasons not worth getting into - the build date on the modules is accurate. The issue should be fixed in any 8.0.4 nightly from within the last two weeks, so if you’re still encountering it it may be a different issue or a regression. ---
**Author:** ![anjoroge](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/anjoroge/32/6698_2.png) [@anjoroge](https://forum.inductiveautomation.com/u/anjoroge)\ **Post date:** [August 9, 2019, 6:49pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/6 "2019-08-09T18:49:13Z")
Hi apgliber, Have you tried modifying the Execution Mode for all your tags including UDT’s to Tag group?. That may help with the issue especially when you are upgrading from 7.9. Thanks, Anthony ---
**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:** [October 18, 2019, 1:46pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/7 "2019-10-18T13:46:26Z")
I run some test with **Ignition 8.0.5** final and I still have the issue with isAlarmActive expression ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/0/04d516a2b4eeace05b8fc92a55b1bbfc623b9949.png) For the same data with **Ignition 7.9.12** : ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e9ecaae33757a0625d714d5dc5ac741185505e66.png) ---
**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:** [October 21, 2019, 3:34pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/8 "2019-10-21T15:34:37Z")
@awalker Is it a known bug of 8.0.5 ? If I replace the expression: ```auto isAlarmActive("[.]../TM/CPU_USAGE") ``` with the full path ```auto isAlarmActive("[default]TVG/SYS/ESX01/00001/TM/CPU_USAGE") ``` I still have the issue ---
**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\ **Post date:** [October 25, 2019, 12:55am UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/9 "2019-10-25T00:55:52Z")
Can you try the latest 8.0.6 nightly and see if you have the same issue? I can reproduce this on 8.0.5, but not on 8.0.6. Still trying to figure out why. Also, there’s a known issue with using `isAlarmActive` and the Event Driven execution mode setting of a tag. That hasn’t been addressed yet, so you’ll need to account for that in your 8.0.6 testing (i.e., try either using Tag Groups or a Fixed Rate). ---
**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:** [October 25, 2019, 2:11pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/10 "2019-10-25T14:11:49Z")
Hi @James.Lorenz, I've upgraded to the last 8.0.6 nightly build. The issue with isAlarmActive is ok...But I have another issue with this expression tag. **I think the issue occur for the result of isAlarmActive when there are disabled alarms (or perhaps all disabled) in the path of isAlarmActive("path")** I confirm this bug is too in **7.9.12** perhaps the same bug as: > [@isAlarmActiveFiltered throws REFERENCE\_NOT\_FOUND when alarms not enabled](http://forum.inductiveautomation.com/t/isalarmactivefiltered-throws-reference-not-found-when-alarms-not-enabled/23933): > > Howdy, I’m trying to implement a client-configurable alarming system within Ignition 7.9.10. I have configurable setpoints and ‘enable’ tags that the alarmed tag references in its configuration. I also have some expression tags that attempt to summarize the current alarm information for a given tag. The issue I’ve found is that the isAlarmsActiveFiltered expression throws a REFERENCE\_NOT\_FOUND exception if there are no alarms enabled on the given tag. I can see why this would be the default … Example: I have one alarm for these expression tag value: [default]TVG/SYS/ESX01/00001/TA/DEF\_CPU\_USAGE Value expression: ```auto isAlarmActive("[.]../TM/CPU_USAGE") ``` Enabled properties of the alarm is bind to an expression ```auto !({[.]../TC/INHIBER_ALARMES} || {[.]../TS/COND_INHIB_ALARMES}) ``` If the enable expression return **True** , the value is OK. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/349010515ad61828d81979a909064133f054f714.png) If the enable expression return **False** , the value go to Bad\_NotFound ! ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/3e6d7e04818d2ead25779a9b3c5e64b912062130.png) I use the same pattern to disable alarm based on other expression tag with no problem. **I think the issue occur for the result of isAlarmActive when there are disabled alarms (or perhaps all disabled) in the path of isAlarmActive("path")** ---
**Author:** ![stuart.williams](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/stuart.williams/32/42310_2.png) [@stuart.williams](https://forum.inductiveautomation.com/u/stuart.williams)\ **Post date:** [August 18, 2020, 4:56pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/11 "2020-08-18T16:56:44Z")
I am experiencing this issue in 8.0.15 outlined [in this post](http://forum.inductiveautomation.com/t/disabling-a-lower-priority-alarm-via-scripting-expression/37813). Has anyone found a workaround? Thanks ---
**Author:** ![mpoulsen921](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mpoulsen921](https://forum.inductiveautomation.com/u/mpoulsen921)\ **Post date:** [June 8, 2021, 11:45am UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/12 "2021-06-08T11:45:22Z")
Hi James, Is there still an issue with the IsAlarmActive on expression tags with execution mode set to event driven? I am using version 8.1.5. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 8, 2021, 11:46am UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/13 "2021-06-08T11:46:29Z")
> [@mpoulsen921](#): > > version 8.1.15. Time traveling from 2022? ---
**Author:** ![mpoulsen921](https://avatars.discourse-cdn.com/v4/letter/m/b4bc9f/32.png) [@mpoulsen921](https://forum.inductiveautomation.com/u/mpoulsen921)\ **Post date:** [June 8, 2021, 11:50am UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/14 "2021-06-08T11:50:37Z")
Whoops, that went to fast. 😬 ---
**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\ **Post date:** [November 2, 2021, 8:17pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/15 "2021-11-02T20:17:04Z")
Is this still a problem in certain circumstances? I'm seeing the following error on `isAlarmActive` and `isAlarmActiveFiltered` ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/5/950448e526cef61e9b24a5da5b870eda9acac5bd.png) where `tagPath` = `[]Substation/PQM-1/Frequency` We generally set the default tag provider at the project level and just refer to `[]` so as to allow our references to be more portable across various Ignition environments and projects. ---
**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\ **Post date:** [January 12, 2022, 7:45pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/16 "2022-01-12T19:45:55Z")
I came back to this and it still seems like an active bug. I'm running **8.1.10 (b2021090812)**. My workaround is to force the tag path references back to a named tag provider with the `replace` function: `replace({view.params.tagPath},"[]","[default]")` ---
**Author:** ![CraigP](https://avatars.discourse-cdn.com/v4/letter/c/ce73a5/32.png) [@CraigP](https://forum.inductiveautomation.com/u/CraigP)\ **Post date:** [February 7, 2022, 5:09pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/17 "2022-02-07T17:09:03Z")
Shouldn’t this work according to the documentation? I’m running 8.1.14 (b2022012711). ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/7/974d0ce67a8b0859e31296182d8c8488f25cd54b.png) ---
**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 7, 2022, 5:22pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/18 "2022-02-07T17:22:54Z")
As [the documentation](https://docs.inductiveautomation.com/display/DOC81/isAlarmActive) notes: > When calling this from the Gateway or Perspective Session scope, the Tag Provider must be included in the path. ---
**Author:** ![CraigP](https://avatars.discourse-cdn.com/v4/letter/c/ce73a5/32.png) [@CraigP](https://forum.inductiveautomation.com/u/CraigP)\ **Post date:** [February 7, 2022, 5:38pm UTC](https://forum.inductiveautomation.com/t/bug-13866-expression-isalarmactive-invalid-relative-tag-path/25536/19 "2022-02-07T17:38:47Z")
isAlarmActive("[default]\*") works. Thanks.