You can also use the Selblocks plugin, which implements the catch method, to catch the error and continue the script anyway. try / catch / finally block An attempt can provide special handling when an error occurs and can guarantee the execution of, for example, the "clear" logic.
The catch block indicates what to do if an error is selected in the try block. That is, if an operator in a try block or in a function or subfunction called from a try block throws an error, then control passes to the corresponding catch block and the error is cleared. If an error does not occur in the try block, then the catch block is skipped. Catch intercepts the given error by matching its error message, which is indicated as a "substring" or as / regular expression /. Lack of specification will catch all errors.
The finally block is executed after the try and catch blocks. It always runs regardless of whether an error is selected or not. It is executed even if the try or catch block is completed using the "change flow" commands: the continue, break, return, or exitTest commands.
Lock attempts may be nested. If the internal attempt does not catch the error, the attached try / catch is entered. The contents of all nested blocks (blocks) are finally completed, the most internal - external - again, even if errors (errors) are encountered along this path.
Both catch and, finally, are optional, but if they are not specified, the attempt simply has no effect.
An optional identifier can be specified in try and endTry, which will be checked for proper pairing.
Try / catch / finally example try | outdoor try | domestic quit | "blamo" getEval | alert ("this warning will NOT be executed") eventually getEval | alerts ("first") endTry | internal catch | / blamo / getEval | alerts (second) endTry | outdoor you can read here http://refactoror.wikia.com/wiki/Selblocks_Reference