# Using Scripting resources within Alarm Notification Pipeline not working

**URL:** <https://forum.inductiveautomation.com/t/using-scripting-resources-within-alarm-notification-pipeline-not-working/33011>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [March 11, 2020, 3:48pm UTC](https://forum.inductiveautomation.com/t/using-scripting-resources-within-alarm-notification-pipeline-not-working/33011 "2020-03-11T15:48:03Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [March 11, 2020, 7:12pm UTC](https://forum.inductiveautomation.com/t/using-scripting-resources-within-alarm-notification-pipeline-not-working/33011/2 "2020-03-11T19:12:04Z")

</div>

Sometimes the Jython instances don’t refresh/reload the imports right away.

I’ve found I can usually force a refresh if I make a trivial edit in the script in Designer then close the script and hit save.

Other things can apparently lead to this, for example [reusing script file names between multiple projects](http://forum.inductiveautomation.com/t/project-scripts-randomly-inaccessible-for-short-period/31043).

Also maybe read the links in that thread in the paragraph starting “I tried searching around in the forum…”

---

_[View the full topic](https://forum.inductiveautomation.com/t/using-scripting-resources-within-alarm-notification-pipeline-not-working/33011)._