There is a solution - "If Object" operation for keyword tests and "WaitChild" for script code.
As mentioned, exception handling is not going to work on this. Instead, what you're going to have to do is make your code "smarter". For those points where object recognition is failing or similar things, you'll need to add logic to break out of the loop on those errors. In pseudo-code:
if (!Aliases.myApp.parentObject.WaitAliasChild("childObject", 5000).Exists) then
End Loop
This is actually a recommended best practice for any situation where you aren't sure that the object is going to apear in time and that object existence is part of the test.
Thanks for the answer.
I succeeded to pu it in place, but I'm obligated to put it on every line (about 40/50 lines). childObject isn't generic; there is no generic solution ? without specifying a childobjet ?
The error can be everywhere, jsute because of a slow response or it was too fast.
