If there is an unexpected exception or error, then the bot should ensure that we bring the target application to a stable state where it can proceed with the next transactions. The following few steps guarantee this:

1. Within the Else block, to ensure that the target application is in a stable state, we will attach an element on the screen to the browser. Let's add a new Attach Browser activity to handle the error handling activity in the already opened Chrome browser:

2. On the properties side of Attach Browser, update Browser with the ZohoBrowser variable and set the BrowserType as Chrome to continue to use the same browser session:

3. Add a Mouse Click activity to the newly created sequence and click on Indicate element inside the browser. Then, go to the browser, and click on the TICKETS menu option in the top left-hand corner of the Zoho desk screen:

This step will enable automation to get control of the home page of the web application if a ticket has not been created.

This completes the Try block. Now, let's handle any system exceptions. 

4. Moving out of the overall Try block, let's update the Catches block. Add a new catch of the System.exception type to the Catches block. Copy the error handling sequence that we added in the Else block and paste it into this Catches block:

So we have now completed the web (Zoho Desk) automation as well. Here, we took the request data and incorporated it into Zoho Desk. Finally, we will go to the main workflow, invoke this workflow, and finalize the automation.