Consider automation a web page. We might have a task that enters some text in an input field and clicks on a submission button. Our expectation is that what happens next is that a new web page is presented and we enter some new information there. The way this works in Automation Anywhere is that we perform a command step to enter some data, perform a command step to click a button and then perform a last command step to enter some data on the new page. There is a problem here. What about latency between the click of the button on the first page and the appearance of the second page? Our last step has us enter some new text on the second page but what if that page is not present?
Thankfully, Automation Anywhere has provided us a solution for just that kind of a problem. When we perform a step against a page, we will find that we are prepared to wait for a configurable period of time for the page to be in the correct state for us to enter the data. The default is 30 seconds. If after that period the page has not reached the state where we can enter new data, then we will throw an error which has a default result of causing the task to come to an end. If we wish, we can then either tweak the timeout value to increase it to be as long as needed for the page to appear or else we can leverage an Automation Anywhere error handler. Surrounding a step with an error handler results in the execution of additional/alternate logic if and when an error is encountered.
In the following video we illustrate what happens when a web page is slow to respond and results in a timeout. We also look at using an error handler to surround such an occurrence to allow us to perform manual action to recover.