June 18, 2020

Exception handling


Ena Martinek

When we're doing some processes manually, we can usually detect an error in it ourselves.

However, what happens when the error occurs in the robotically automated process? Are robots capable of handling the situation?

To help robots out, we developed the Exception Handling section for every process and its specific requirements. In other words, instead of having a few generic exceptions, Exception Handling is a part of the process. It is custom-made by developers, based on the process's needs, and executed only if an error occurs.

In that case, the process stops, and the robot starts the Exception Handling section. For example, in Exception Handling, you can implement email notifications to the responsible person, log the error, close all the applications used in the process, or any other customized action your process needs.

In each Exception Handling section, besides the variables used in the process, you will have specific generic variables with values of those exact errors, such as:

ErrorTimestamp - Time when the error occurred.
ProcessName - The name of the process.
StepNameWhereTheErrorHappened - The step name where the error appears. You can name each step differently, so you will know where exactly in the process is the error located.
ApplicationScreenshot - Screenshot of the window when the error appeared.
RobotName - Name of the robot that executed that process.
ExceptionMessage - Exception message sent when the error in the process occurred.
CustomErrorMessage - Message you can define for each step differently.

The Exception Handling section can have multiple flows, depending on the error type, due to “StepNameWhereTheErrorHappened” and “CustomErrorMessage”variables.
With them, you can predict some errors in advance and create exceptions for them.

Picture 1: example of Exception Handling sectorPicture 1: example of Exception Handling sector

Also, you can use the same Exception Handling section for more than one process. For that, you have to create an external procedure for handling errors and execute it in the Exception Handling section.
Thank you for leaving a message!
Other posts
  • Procedures


    Ena Martinek


    July 21, 2020

    Based on our RPA consulting experience, we developed a "Procedures" feature to help you manage big projects without copying the same code in multiple...

  • RPA Developer and Business Analyst – do we need both?


    Darko Jovišić


    June 16, 2020

    Generally, in RPA team blueprints, you will find these two roles among others: RPA Developer and Business Analyst. In a nutshell, a business analyst should...