This is an interesting one. If the error is thrown after the code below is executed, we'll have two code paths leading to some of the same instruments exit handling logic, I think. Not sure of a good way to address this right now without creating more instance variables.