If unhandled errors are raised within the process, the workflow execution continues with this section. Unhandled errors are identified by the system and are not previously known to the user. These are technical exceptions, such as an activity failing due to Internet connection problems or unavailable Web sites.
When a system exception is thrown, the unhandled error section is executed and a screenshot is taken by the default TakeScreenshot activity. In addition, the Clean Application Exit activity executes at the beginning of this block to ensure a blank screen before the defined activity begins. This ensures that the block is equally usable for errors of different types and at different points in the process.
At the end of this section, the Rethrow activity rethrows the previous error to provide this information to the user. The user can specify an error remark and ID for the error. We recommend that users rethrow the error remark that was thrown by the system. The default Raise Error activity is already set up to do this. The error is written to the database and can be viewed in Hyland RPA Manager.