# Setting the delay via scripting in alarm pipeline

**URL:** <https://forum.inductiveautomation.com/t/setting-the-delay-via-scripting-in-alarm-pipeline/23882>\
**Category:** Ignition Early Access\
**Created:** [April 5, 2019, 8:04pm UTC](https://forum.inductiveautomation.com/t/setting-the-delay-via-scripting-in-alarm-pipeline/23882 "2019-04-05T20:04:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sudipta.tripathy](https://avatars.discourse-cdn.com/v4/letter/s/c57346/32.png) [@sudipta.tripathy](https://forum.inductiveautomation.com/u/sudipta.tripathy)\
**Post date:** [April 5, 2019, 8:04pm UTC](https://forum.inductiveautomation.com/t/setting-the-delay-via-scripting-in-alarm-pipeline/23882/1 "2019-04-05T20:04:49Z")

</div>

Can I set the delay block via scripting in alarm notification pipeline in when roster type in calculated?

---

<div class="post-metadata">

**Author:** ![mhickerson](https://avatars.discourse-cdn.com/v4/letter/m/9de0a6/32.png) [@mhickerson](https://forum.inductiveautomation.com/u/mhickerson)\
**Post date:** [April 9, 2019, 8:18pm UTC](https://forum.inductiveautomation.com/t/setting-the-delay-via-scripting-in-alarm-pipeline/23882/2 "2019-04-09T20:18:23Z")

</div>

While you can’t access or modify a delay block from scripting, you should be able to achieve the same results inside the pipeline using Set Property and Switch blocks to route to different delays. Hope this helps.
