# Using RunScript in Pipeline Expression

**URL:** <https://forum.inductiveautomation.com/t/using-runscript-in-pipeline-expression/19047>\
**Category:** Ignition\
**Tags:** ignition78\
**Created:** [August 1, 2018, 1:55pm UTC](https://forum.inductiveautomation.com/t/using-runscript-in-pipeline-expression/19047 "2018-08-01T13:55:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![oisin.gribben](https://avatars.discourse-cdn.com/v4/letter/o/9d8465/32.png) [@oisin.gribben](https://forum.inductiveautomation.com/u/oisin.gribben)\
**Post date:** [August 1, 2018, 1:55pm UTC](https://forum.inductiveautomation.com/t/using-runscript-in-pipeline-expression/19047/1 "2018-08-01T13:55:54Z")

</div>

I am trying to use a runScript in an expression for an alarm pipeline.  
I have test the the script works in a normal expression tag but it doesn’t in the pipeline expression.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 1, 2018, 6:43pm UTC](https://forum.inductiveautomation.com/t/using-runscript-in-pipeline-expression/19047/2 "2018-08-01T18:43:17Z")

</div>

[Um?](http://www.catb.org/esr/faqs/smart-questions.html)  
I would guess there’s something about the environment of a pipeline that makes a difference. I can’t tell from your question what it could possibly be. Looking for errors from your script in the gateway log might be a good start.