Lets take one scenario, you configured your robot and while at the time of unit testing, it throws exception in selectors at some point but it will close everything and pick the next transaction, that way you have to go back again at that point manually. But in my cases you cannot open that transaction again which is failed.
What my point is, i know the selector is changing at this point so i put something like message box at that point and trigger my bot. So message box popups at that point in my next transaction then i will configure that selector at run time and robot will process further. That way i need not to stop the bot and i can do testing end to end.
Also we can think like that, at the time of exception, it gives you option whether you want to fix your error and move forward or you want to go to next configured step incase of error