Pipeline Acknowledge

Hello everyone!,

I have a question about how to receive emails for acknowledged alarms. Currently, I receive active alarms correctly, but if a user acknowledges them, I don't receive any notifications.

I have been researching in the forums, and I came across this method 'system.alarm.acknowledge,' but I am not sure where to incorporate it.

Should I use a script in a component with an 'onAcknowledge' function, or should I directly add a script in the notification pipeline?

What is exactly the best way to receive these emails?

many regards.

something like that?

You don't need any extra blocks or scripting functions to receive an email when an alarm is Acked.

You are likely running into the Alarm Notification Pipeline Dropout Conditions. By default, a Pipeline will stop running when the Alarm is cleared, acked, or shelved. If you want the Pipeline to keep running during these events you would need to set the Dropout Condition Boolean to false on the Alarm Pipeline. You would also need to ensure the Alarm properties on the Tag are setup to send a notification on the "Ack Pipeline" property.

Take a look at the Ack Pipeline section on this User Manual page: Adding Pipelines to Tags - Ignition User Manual 8.1 - Ignition Documentation

You can edit the Dropout Conditions by selecting the Pipeline in the Project Browser and using the Block Editor panel.

good morning and sorry for the delay in responding,

I will show the configuration that I have

this is a test alarm that I created with the configuration that I normally use in the pipeline alarms, note that I have Ack Pipeline notifications activated and associated to the

alarm activates correctly (I receive mail without problems)

after acked the alarm goes to acknowled correctly, but the problem is that I am not receiving any mail related to acked
image

Am I skipping any settings? any recommendations?

thank you very much

additionally these are the properties I have right now

image

Hey Miguel,

Not sure if your issue is resolved, but I'm guessing the pipeline never drops out. Login to the status screen of the gateway using a web browser and look at the state of your pipelines. There might be some useful information there.

I'm currently looking at how can I trigger the dropout conditions manually from inside the pipeline. This is to be able to have all dropout conditions off like you but still be in control on when the pipeline drops. Let me know if you have any insights!