Any time the user updates a field, or enters a new layout, I run a script. This works fine on FileMaker Pro and WebDirect, but the script triggers stopped triggering on Go. Not sure what is causing this, because they did work for a time. Buttons still work, but the requirements don't allow for the user to have to press a button every time they change the search parameters. Does anyone know what could be causing this behavior?

Edited March 2, 20169 yr by mmarino

I just saw a video by Richard Carlton about this. Landlines in FileMaker

2 hours ago, Lee Smith said:

I just saw a video by Richard Carlton about this. Landlines in FileMaker

I watched the video. That is about scripts that enter other fields which have script triggers in them, causing those scripts to run when they aren't supposed to. This doesn't address my issue.

I missed read the question. What does the script do? 

15 hours ago, Lee Smith said:

I missed read the question. What does the script do? 

It's not limited to a single script. Any script I assign won't trigger. Buttons will trigger, but not script triggers like onobjectvalidate.

Apparently we just needed to restart the app and that fixed it.