Why are regular scripting errors not exceptions? It seems arbitrary that this particular case would be treated as a regular scipriting error rather than treating it as an exception and allowing me to handle it a manner useful to my test.
In my particular case, the process is busy causing this object to become unusable. I could get around this by increasing the Options.Run.Timeout to something much much higher. However, I am trying to move my code to a script extension to make it shareable and I have not yet found away change playback properties from a script extension.
Ideally, this, and all script "regular" errors would be treated as exceptions unless I specfically say its an error via Log.Error().