Common Exceptions
Below you can find the most common exceptions that you can encounter in projects developed with UiPath. As a general note, all exceptions are types derived from System.Exception, so using this generic type in a Try Catch, for example, will catch all types of errors.
- NullReferenceException - This error usually occurs when using a variable with no set value (not initialized).
- IndexOutOfRangeException - Occurs when the index of an object is out of the limits of the collection.
- ArgumentException - Is thrown when a method is invoked and at least one of the passed arguments does not meet the parameter specification of the called method.
- SelectorNotFoundException - Is thrown when the robot is unable to find the designated selector for an activity in the target app within the TimeOut period.
- ImageOperationException - Occurs when an image is not found within the TimeOut period.
- TextNotFoundException - Occurs when the indicated text is not found within the TimeOut period.
- ApplicationException - describes an error rooted in a technical issue, such as an application that is not responding.
|
Business Rule Exceptions are separate from all the System Exceptions listed above. These describe errors rooted in the fact that certain data which the automation project depends on is incomplete, missing, outside of set boundaries (like trying to extract more from the ATM than the daily limit) or does not pass other data validation criteria (like an invoice amount containing letters). The Business Rule Exceptions will not be thrown by using the generic System.Exception in a Try Catch activity. The mechanism of handling this exception has to be separately defined by the developer (based on the rules set by the process owner), or it can be reduced to stopping the execution of the process, by using a simple Throw activity, for example. |
Try Catch Finally
 |
 |
 |
ContinueOnError Property
Continue on Error is a property that specifies if the execution should continue even when the activity throws an error.
Keep in mind that, if the ContinueOnError is set to True on an activity that has a scope (such as Attach Window or Attach Browser), then all the errors that occur in other activities inside that scope are also ignored.
Having this property set to true is not recommended in all situations, but there are some situations in which it makes sense, such as:
- while using data scraping - so the activity doesn't throw an error on the last page (when the selector of the 'Next' button is no longer found);
- when we are not interested in capturing the error, but simply in the execution of the activity.
'프로그래밍 > RPA' 카테고리의 다른 글
| IS 와 Equals의 차이점 (2) | 2020.04.16 |
|---|---|
| Orchestrator / Queue / SLA (0) | 2020.04.08 |
| 폴더 안의 여러개의 파일 읽는 방법 (0) | 2020.03.26 |
| Read Text File character encoding property (0) | 2020.03.26 |
| DataTable의 Column 이동하기(순서 바꾸기) (4) | 2020.03.25 |
