Handle errors in RPA Desktop Design Studio

  • Release version: Australia
  • Updated March 12, 2026
  • 1 minute to read

    • Handle errors at the component level and activity level in RPA Desktop Design Studio. You can use the Error Handler option to handle the errors that occur during an automation execution.

    Before you begin

    Configure a component. For more information, see Use a component in RPA Desktop Design Studio.

    Create an activity. For more information, see Create and use an activity in RPA Desktop Design Studio.

    Role required: none

    Procedure

    1. In the RPA Desktop Design Studio, select one of the following options to handle errors either at a component level or at an activity level.
      OptionAction and description
      To handle errors at a component level On the Design surface, right-click the component title bar and select Error Handler to open the ERROR HANDLER dialog box.
      To handle errors at an activity level In the Project Explorer pane, right-click an activity and select Error Handler to open the ERROR HANDLER dialog box.

      By default, error handling at the activity level applies to all components within that activity, except for the components where errors handling is explicitly configured.
    2. In the ERROR HANDLER dialog box, from the On Error list, select any one of the following error handler types:
      Type Description
      Inherit Inherits the error handling settings that are configured at the parent level.

      Within a component, an activity that the component belongs to, is the parent. Within an activity, the parent is the activity where the activity is being called from.

      This option is the default for error handling at component level.
      Stop Stops the execution if error occurs.

      This option is the default for error handling at the activity level.
      Continue Continues the execution if an error occurs.
      Retry Retries the execution of the component where the error occurs.
      After selecting the Retry option, the following fields appear:
      • In the Max Retries field, you can define the number of retries.
      • In the Retry Delay field, you can define the delay between each retry.

      The automation stops with an error if the Maximum retires count is exhausted during an execution.

      In the On Error After Retry field, you can select an option such as Inherit, Stop, and Continue to provide further steps if an error persists after a defined retry has failed.
    3. Click OK.