Turning it into a function with a sealed workspace would make it easier. But a try-catch would work with this in that case. Theoretically it would work with a script too, but having the workspace fully exposed is not ideal even though the second run should presumably just overwrite everything from the first run anyway.
try
myFunction( )
catch
myFunction( )
end
should be enough to do it though. So long as it isn't in a loop this will only re-run it once and then the error will just land on your command window as normal after the 2nd time.
Blanket error catching like this is not generally advisable though as even basic syntax errors will just result in it attempting to run a second time pointlessly before reporting your error, but I understand it can be difficult if you get a bunch of different hardware errors with identifiers you don't necessarily know.
