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.
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).