Basically, you need to tell the system that when a certain type of failure occurs, you want the engine to Go To a certain step in the script. In order for that to happen, you need to tell the system your intentions prior to the failure. I like to either put my exception handlers at the top of the script, or just before a step I know is likely to fail.
The quickest way to set yourself up is to use the On Exception Goto step and pick the WFExecutionException (fourth from bottom) and choose a label to go to when that happens.
I can tell you that if the site is offline, the normal HTTP timeout will need to expire first before the exception will be thrown. To prove that, reactive debug your script and see how long the HTTP call sits there before failing.
Here's an exception handling helper utility script I made which could tell you what exact exception to pick.
https://supportforums.cisco.com/docs/DOC-26839
Lastly, you really don't even need the On Exception Clear step. It's use is simply to negate a On Exception Goto step. If you design your script properly, you could end up not even using it. However, if you're just learning, the best place to use it is right after the label you're sending the On Exception Goto step to. Be sure to pick the same exception in the On Exception Clears step as you did in the On Exception Goto step. Remember it's cancelling the handler for a specific exception you set earlier.
Good luck and happy exception handling.
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.
