When the data is not accessible, the created table displays only the header row, and processing for that client must be halted, a BusinessRuleException occurs. A BusinessRuleException is a type of exception that indicates a business logic error or a validation error that cannot be resolved by retrying the transaction. For example, if the input data is incorrect, incomplete, or outdated, a BusinessRuleException should be thrown. A BusinessRuleException can be thrown by using the Throw activity with the following expression:

VB New BusinessRuleException(“Message”) where Message is a string that describes the error. A BusinessRuleException can be caught by using the Catch activity with the following expression:

VB ex As BusinessRuleException where ex is a variable that stores the exception object. A BusinessRuleException can be handled differently from other types of exceptions, such as SystemException or ApplicationException, depending on the logic of the automation. For example, in the REFramework, a BusinessRuleException sets the status of the transaction item to Failed and does not retry the transaction, whereas a SystemException sets the status of the transaction item to Retry and retries the transaction up to a specified number of times. References: [BusinessRuleException], [Throw], [Catch], [REFramework]