If I do a file delete and the file is locked by another process for some reason is there a way to trap the error so the job doesn't abort? Would I have to set the job to ignore execution errors to do that?

Enable "ignore execution errors" and after FileDelete use FileExists check if the file still exists. If yes, it was not deleted

: If I do a file delete and the file is locked by another process for some
: reason is there a way to trap the error so the job doesn't abort? Would I
: have to set the job to ignore execution errors to do that?