# Ignition Alarm Pipeline, dynamic / scripted jump **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [August 4, 2021, 2:31pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555 "2021-08-04T14:31:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [August 4, 2021, 2:31pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555/1 "2021-08-04T14:31:08Z")
Hi, is it possible to have inside an alarm pipeline a scripted / dynamic Jump block? I have a pipeline which already extrapolates the site of the alarm and I would like to jump to an ad-hoc pipeline named as the site. ![jump](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/4/f4c314d6575dfad80b4a148626310d122b127eaa.png) currently we have several sites and need to create a single jump for each site and add a jump block each time a new site is setup. At the moment it seems the jump block allows only to select already created pipelines from a dropdown. ![pipeline_jump](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/b/abab59e9059b5726b3734cc24e90d4e8dd3aa090.png) Thank you ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [August 4, 2021, 2:57pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555/2 "2021-08-04T14:57:30Z")
No, this isn’t possible. You could `switch` on the property, and have a series of manually added jumps; how often are you going to be adding new sites? ---
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [August 4, 2021, 3:12pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555/3 "2021-08-04T15:12:06Z")
> [@paul-griffith](#): > > `switch` on the property, and have a series of manually added jumps; In the old Vision platform we already have a big switch with 50+ sites which makes navigation in the Pipeline difficult, in the new Perspective platform we will reach that number very soon so I hoped we could make things tidier this time with a dynamic jump and a separate pipeline for each site. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [August 4, 2021, 3:19pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555/4 "2021-08-04T15:19:21Z")
Ouch. Yeah, it’s not currently possible; I’d suggest filing a feature request on [ideas.inductiveautomation.com](http://ideas.inductiveautomation.com), but that won’t help you out much in the short term. What’s different between these 50+ sites? Do they all actually need separate pipelines? Maybe some could be consolidated and use dynamic rosters/calculated rosters? ---
**Author:** ![r.p](https://avatars.discourse-cdn.com/v4/letter/r/71e660/32.png) [@r.p](https://forum.inductiveautomation.com/u/r.p)\ **Post date:** [August 4, 2021, 3:26pm UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555/5 "2021-08-04T15:26:12Z")
We could probably consolidate some pipelines, but it would then be more work to realize each time which pipeline does what and then merge/split pipelines accordingly, in the end it’s easier for us to copy a standard pipeline each time a new site is added and specialize it when needed. Thank you I’ll post in the feature request, I just wanted to make sure it is currently not feasible. ---
**Author:** ![drojas](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drojas/32/3403_2.png) [@drojas](https://forum.inductiveautomation.com/u/drojas)\ **Post date:** [April 14, 2023, 1:25am UTC](https://forum.inductiveautomation.com/t/ignition-alarm-pipeline-dynamic-scripted-jump/49555/6 "2023-04-14T01:25:25Z")
I wanted to bring this topic back to life because there is a specific case why a scripted jump might be necessary. When you have only 1 general/global pipeline that uses dynamic/calculated rosters for different sites, I have seen the case where an alarm from Site A gets queued for calculated Roster A. Then shortly after an alarm from Site B occurs (within the consolidation timeframe) and queues calculated Roster B. Alarm A clears and drops out, but Alarm B persists past the consolidation timeframe and notifies Roster B but it contains alarm B information as well as alarm A information. I think this is because even though the first alarm dropped out, the notification pipeline is still active from the second alarm...and because it is still just 1 global pipeline it doesn't disassociate one notification from another. Creating an individual Notification Block for each site and using a Switch block...or creating a new pipeline for each site can prove inefficient when the number of sites grows (and looks messy). Especially if you want to make a change to the pipeline logic. If perhaps there was a way to instantiate an array/list of notifications on the fly....or create new pipelines based off of a template...that might help. If there is anyone that has implemented this in a different fashion, I'm sure there are others that would like to know how it was done. Thanks.