# Alarm pipeline: calculated roster and consolidation

**URL:** <https://forum.inductiveautomation.com/t/alarm-pipeline-calculated-roster-and-consolidation/66574>\
**Category:** Ignition\
**Created:** [November 16, 2022, 10:05am UTC](https://forum.inductiveautomation.com/t/alarm-pipeline-calculated-roster-and-consolidation/66574 "2022-11-16T10:05:24Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![justin.brzozoski](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justin.brzozoski/32/13452_2.png) [@justin.brzozoski](https://forum.inductiveautomation.com/u/justin.brzozoski)\
**Post date:** [November 28, 2022, 3:55pm UTC](https://forum.inductiveautomation.com/t/alarm-pipeline-calculated-roster-and-consolidation/66574/8 "2022-11-28T15:55:55Z")

</div>

Coming in since you pinged me on my [old related thread](https://forum.inductiveautomation.com/t/consolidated-alarms-calculated-rosters-and-custom-messages-oh-my/48548/4).

Sadly, we never found a solution and have had to leave consolidation disabled.

If push comes to shove, my next step is going to be to abandon Ignition pipelines almost entirely, and script EVERYTHING. I would leave a simple pipeline that sends the alarm events to a script, and do all the other management myself. There are APIs to send Twilio messages and emails, which i would use instead of the built-in alarm notification pipeline blocks.

I really wish the built-in consolidation features could consolidate per recipient email or phone-number, and not per event or per pipeline or whatever it does right now.

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-pipeline-calculated-roster-and-consolidation/66574)._