If there is a business exception you’ll need to instruct the robot to throw the process, using a throw activity, because it’s business logic. Within that throw you could type:
new BusinessRuleException(“Your exception message here”)
as long as it is within the try section of a try catch.
The catch should have a ‘businessRuleException’ added, and within that catch you can specify what the robot does with the exception message. You can reference it with “exception”, so for example if you wanted to log the message, you would log “exception.message” and it would appear in the output pane of studio.
If you do not surround the activities with a try catch, the throw activity will fault the workflow completely.