# Multiple Alarm Pipelines Sharing One On-Call Roster **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [July 24, 2023, 7:36pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810 "2023-07-24T19:36:13Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Icey\_Wang](https://avatars.discourse-cdn.com/v4/letter/i/e9bcb4/32.png) [@Icey\_Wang](https://forum.inductiveautomation.com/u/Icey_Wang)\ **Post date:** [July 24, 2023, 7:36pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/1 "2023-07-24T19:36:13Z")
I'm trying to generate several alarms via email. Can I use only one on-call roster for several alarm pipelines? ---
**Author:** ![zbinder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zbinder/32/28918_2.png) [@zbinder](https://forum.inductiveautomation.com/u/zbinder)\ **Post date:** [July 26, 2023, 2:04pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/2 "2023-07-26T14:04:57Z")
You should be able to mix and match pipelines/rosters however you like. You can even use the same roster multiple times in _one_ pipeline. Have you encountered any issues? ---
**Author:** ![Icey\_Wang](https://avatars.discourse-cdn.com/v4/letter/i/e9bcb4/32.png) [@Icey\_Wang](https://forum.inductiveautomation.com/u/Icey_Wang)\ **Post date:** [July 27, 2023, 7:44pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/3 "2023-07-27T19:44:55Z")
I tried those ways. But I'm facing a problem. When I finished setting up the alarm pipeline, on-call roster and triggered the alarm in PLC, only several people of on-call roster could receive the email from ignition. The others were not able to receive the email. I'm sort of lost. ---
**Author:** ![zbinder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zbinder/32/28918_2.png) [@zbinder](https://forum.inductiveautomation.com/u/zbinder)\ **Post date:** [July 27, 2023, 8:06pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/4 "2023-07-27T20:06:00Z")
Hard to say what's happening without more detail, but this doesn't sound like a pipeline issue. Is it the same users that you can't reach every time, and do they have anything in common? Have you confirmed that you can reach them at all? Try going to Email Settings and sending a test e-mail to make sure that you're able to reach them. ---
**Author:** ![Icey\_Wang](https://avatars.discourse-cdn.com/v4/letter/i/e9bcb4/32.png) [@Icey\_Wang](https://forum.inductiveautomation.com/u/Icey_Wang)\ **Post date:** [August 1, 2023, 6:04pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/5 "2023-08-01T18:04:37Z")
Just figured it out. I was using an examine-on instruction to trigger the alarm pipeline. I changed the tag to an output bit. Now it's working fine. But still confused, I don't know the reason why only several people could get the email when I was using the examine-on (a push button) condition. ---
**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\ **Post date:** [August 1, 2023, 6:53pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/6 "2023-08-01T18:53:28Z")
Did you have the pipeline set up to drop out on alarm clear? If the bit went back to false in the middle of sending out emails, it would just stop and not send the rest of the emails, in my experience. EDIT: Just checked the manual and it does mention this behavior as intended: [Ignition 8.1 Manual - Alarm Notification Pipelines](https://docs.inductiveautomation.com/display/DOC81/Alarm+Notification+Pipelines#AlarmNotificationPipelines-ToDisplayandModifytheProperties) > ...In addition, the dropout condition is checked in-between notifications, so **if the condition is met while a notification block is partway through notifying users in a roster, no further users in the roster will receive a notification.** (emphasis mine) ---
**Author:** ![Icey\_Wang](https://avatars.discourse-cdn.com/v4/letter/i/e9bcb4/32.png) [@Icey\_Wang](https://forum.inductiveautomation.com/u/Icey_Wang)\ **Post date:** [August 1, 2023, 7:17pm UTC](https://forum.inductiveautomation.com/t/multiple-alarm-pipelines-sharing-one-on-call-roster/76810/7 "2023-08-01T19:17:29Z")
Makes sense. I was using a momentary push button to trigger it.