AnsweredAssumed Answered

Abort server schedule

Question asked by DavidJondreau on Sep 8, 2014
Latest reply on Sep 9, 2014 by wimdecorte

Is it common for a scheduled script that is set to Abort after time limit is reached to keep the user logged in?

 

I have a problem with a FileMaker server scheduled script. It's a listener, set to run every 15 minutes. It's got a script time limit of 12 minutes and it is set to abort when that time limit is reached.

 

The script checks to see if there are any records flagged, and if so, sends an e-mail for each record and resets the flag.

 

It runs ok, sometimes for a week, sometimes just a day, and then chokes on something. I can't figure out what is causing the script to hang. But when it does, it never aborts. The error logs show "time limit exceeded or server stopped" but the server "user" stays logged in and the database server gets completely stalled. No users can successfully log in (including all subsequent server scripts) and we have to restart the entire machine. It's a total meltdown.

 

I've considered the possibility that it's not the script hanging, but the server itself, and the script hanging is a symptom. That doesn't seem to be the case. If I turn off that scheduled script, I never run into a hang state.

 

I'm working on the script itself, but what I don't understand is why doesn't the server script abort log out the user? Has anyone had success with this abort option?

 

Also, why even have the option to *not* abort the script? Under what circumstances would someone have a time limit and let the script run after the time limit??

Outcomes