I have an alarm pipeline that is set up to email users when a tag is alarmed. The problem is, the alarm isn’t in the ‘active’ state for very long. What this can mean is, when there are multiple users to email, the pipeline can be so slow that the first user will get an email saying the state is ‘Active’ but the other users will see the state as ‘Cleared’.
I have disabled Pipeline Dropout conditions. I want to know if there is a way to maintain the alarm event state throughout the pipeline. I know some cases you don’t want that (for dropout conditions), but i can also see that many people would simply want to treat the alarm as ‘Active’ throughout the timeline of the Pipeline.