The abort is usually very reliable.
A couple of things:
- make sure to refresh the admin console's view by closing all admin consoles and doing a restart on the admin server from the command line
- the most common cose of a schedule being stuck is through a validation error; check any validations you have set up on fields. This behavior is very similar to what a regular client would see: not being able to get out of anything. So check the data that is being processed very carefully. 9 times out of 10 that's where I find the issue
Do you have Allow User Abort[off] in the script?
I don't see any validation issues. The script has been *mostly* "read only" and the fields that get set aren't referenced in a validation calc and doesn't have one themselves.
The solution also has CWP clients logging in, often in response the server script (which is sending e-mails). It's possible there have been record locking conflicts between CWP clients and the server script. So, today, I reduced the script to "read only" except for a single Set Field, which I pre-fix with an Open Record and error capturing, hopefully that solves it.
Unfortunately, I believe the hang has happened when CWP logins were unlikely. I'll set up a session logger on the PHP side (not into FileMaker) which may isolate that.
I've tried doing a command line restart, but it was taking so long, I thought it had hung. Maybe I need to give it more time. What's the longest successful time it could take to get a command line response?
Allow User Abort is set to Off.
a command line restart of the admin server part is usually very very fast. I've never seen it take more than a few seconds, usually much faster.