Currently, (as per TestComplete help) TestComplete only checks for unexpected windows when the script performs an action (Click, DblClick, Activate, etc.). The check does not happen when the scri...
In that case, right your own "recovery scenarios" as separate modular script code functions or keyword tests that handle the situations you need to handle... this is not different than what I already described. For example, one recovery scenario is "path not found". Build a generic piece of code that will execute your recovery scenario for "path not found" instance and then incorporate that into any test case that has the potential for doing so. Even in what you described, you still need to build out the recovery scenario handler... TestComplete doesn't have a feature per se called "recovery scenario" but it has the ability and flexibility for you to add any such code to any test case in a modularized fashion. Again, what you are describing are not "unexpected windows" by TestComplete's definition.. they are "expected possible scenarios" that you need to code for. Just a matter of doing the code for them.