Is there a way to change my coding of scripts so that so-called scripting errors don't show up in server logs when a scheduled script is executed on FM Server? I get dozens of such errors for each daily execution, and Using a Set Error Capture [On] script step doesn't seem to make a difference as to whether the "errors" show up in the server log. The kinds of error codes that do show up (101, 401) don't seem to me to be be the result of scripting errors at all. Rather, they are part of ordinary operations (e.g., testing to see whether to stop looping by checking whether a record exists in a found set).

I raised this question a couple of weeks ago in a much longer email providing a lot of the context that I thought the FM Forum community preferred. I didn't hear back and so have tried to reduce my question here to the bare bones.

these are usually when in a Loop and you go to next record or go to next portal exit after last

for a record you can use Exit Loop if Get(RecordNumber) = Get(FoundCount) 

Thanks for that tip, Ocean. Scripting errors aside, is it bad coding practice to, e.g., make an action conditional on the occurrence of an error on opening a record? The term "scripting error" suggests it is.