# runScript on client tag stops working

**URL:** <https://forum.inductiveautomation.com/t/runscript-on-client-tag-stops-working/24255>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [April 19, 2019, 2:21pm UTC](https://forum.inductiveautomation.com/t/runscript-on-client-tag-stops-working/24255 "2019-04-19T14:21:11Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nick.schuetz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nick.schuetz/32/6160_2.png) [@nick.schuetz](https://forum.inductiveautomation.com/u/nick.schuetz)\
**Post date:** [April 19, 2019, 2:21pm UTC](https://forum.inductiveautomation.com/t/runscript-on-client-tag-stops-working/24255/1 "2019-04-19T14:21:11Z")

</div>

I am seeing where runScript inside of a client tag will work as expected on first log in to a client. But on a sign out, sign in, there is a

`WARN vision.ProjectTag - Error creating tag binding for client tag '[client]ScreenName': Timer already cancelled.`

and the binding shows broken in the client. Moving the runScript to an expression binding directly on the component will work on first sign in, but again signing out and signing back in, it returns an

`illegalStateException: Timer already cancelled`  
[runScript error.txt](https://us1.discourse-cdn.com/inductiveautomation/original/2X/e/e8228f6717d10cd962bbec4a065c07706a189e33.txt) (3.1 KB)

the expression binding is on custom scripts as well as a system script  
`runScript("system.util.getConnectionMode", 1000)`