For all kind of Script Triggered Scripts there is a hard time find the errors if you do not run it on FileMaker Pro Advanced where you can use the Debugger to see what is actually happening.
1. Make sure you do not have any script steps that is not allowed on FMGo
2. Do you have several Script Triggers on Layout/Objects, then it becomes even harder to manage
3. Try/test as much as you can on FMPA and you will see where the problem is
The scripts all work fine on filemaker pro everytime, so I don't think
it's a problem with the actual script, and often the scripts work
temporarily but stop working, ill run them through filemaker advance to
What scripts don't work well on filemaker go
I just came across this problem today working with script triggers in FMGO 15. The triggers would not fire. They worked fine in FileMaker Go 14 and 16. Once I killed the App and restarted the iPad the scripts worked fine in FMGO 15. FMGO has a history of misbehaving if iPads are not restarted.
That is exactly what is happening with my program and likewise if i restart
it it fixes the problem, is there any solution? can i use filemaker go 14
instead of 15? I tried filemaker go 16 but its not compatible with our
server and i do not have the ability for now to update the server
You could try FMGO 14 but I think it might have the same issues. I'm hoping FMGO 16 doesn't have the same problem. This is a common problem but I'm not aware of any official reason for the problem. I'm convinced it is a problem with memory and the temp folder. So far only restarts seem to temporarily solve the problem. There have been quite a few previous discussions about FMGO woes.
Does the same thing happen with the web direct version?
Just use FMGo 16 and see if the issues were resolved. FMGo16 has no issues connecting to FMS14/15.