Make errors such as 101 and 401 exceptions to the server's detection of errors when scripts are running.
And/or move server-side scripting errors into a separate log.
I support this idea, but the reason for this request seems would seem to be to avoid clutter in the server log and to be able to more easily differentiate between real "errors", "warnings" and just "info". For this reason, I'd like to see the server scripting errors moved to a separate server log, an idea I just added at Separate Server-Side Scripting Errors into Separate Log
Amen, brother! This is the most important thing for server side scripting! See my comments on this here: https://community.filemaker.com/ideas/2075
Not sure I agree. When I look at the schedules , I prefer to see an uninterrupted column of "OK" s which is not the case when scripting errors caused by expected 101 or 401 errors are actually false-positive results. It's true that scripts can be rewritten to avoid 101's but trapping for 401's that are expected is a real pain.
Retrieving data ...