When a Robot encounters an error during execution, an exception is thrown. Exceptions inform you that something unexpected happened, but in some cases, exceptions can be handled by the Try Catch step and the robot execution may continue afterwards. In situations when the robot is not configured to handle the exception, the execution does not resume and the exception is passed to the Basic Engine Robot to handle it.

You can see the list of possible exceptions that cannot be handled in the Exceptions section in the Robot Editor.

In this example, the robot may throw four exceptions: three predefined exceptions (DeviceIssue, OverFlowIssue, and DivisionByZeroIssue) and one custom exception (NoUserFound). The list of exceptions cannot be edited and only provides information about the robot.