How do I thwart Unwanted Process Termination?

OK, First, a snippit of keyword code...

RoutingWorkCenterComboBox  ClickItem     "44555 - VERSATECH - BENTEC - *W"
OkActionButton             ClickButton

Pretty standard stuff. That Combo box is an odd duck though. Once you select "OK" it goes and runs a bunch of processes... takes ~ 45 seconds.  While it does this, the form changes from "Change Routing" to "Change Routing (Not Responding)" It is not dead, it is just doing "other things"... This is how the devs coded it, and I can't change that. I selected the OKActionButton and changed the auto-wait timeout to 60 seconds... 90% of the time, this is fine.

So, My issue:

The times it is NOT fine, the "Failure-process" that TC runs differs from the norm. Nrmally, you get a message like "Box xyz not found" and you can trap that and, in code, arrange for a workaround, or branch on "observed" text or... whatever

HOWEVER, In this case, if the Auto-Wait timeout concludes, and TC notices that (Not Responding)... It terminates the offending process!(My program)

The Samtec.ShopFloorControl.AppHost.exe process does not respond. It will be terminated. 

THEN, to make matters worse, it tries to continue my script, which causes all sorts of mayhem as it goes about trying to find stuff on my desktop! (YES, I have Stop on error checked)

So:

1. Is this a bug?

2. If not, How do I change the behavior of the Evil(process)Terminator?

I would be fine with a nomal error toss... something my script can work with. But it is pretty hard to do much when your application is gone.