In Blue Prism, how is exception handling generally achieved?

Exception handling in Blue Prism is primarily achieved with built-in recovery options. This mechanism allows processes to gracefully handle errors or unexpected situations that may arise during execution. It enables the robot to attempt recovery from an error instead of simply failing, which helps in maintaining smoother and uninterrupted operations.

When a process encounters an exception, the built-in recovery options allow for specific actions to be defined that can include retrying an action, invoking alternate paths, or logging the error for further analysis. This robust error handling is crucial for creating resilient automation processes that can function effectively even in dynamic environments where errors might occur.

Using session logs is helpful for tracking execution and identifying issues after they occur, but it does not provide a proactive method to handle exceptions in real-time during the automation process. Manually stopping the process refers to a more hands-on approach that does not utilize any automation capabilities for handling exceptions. Restarting the machine is not relevant to exception handling within Blue Prism, as it does not address the root cause of errors occurring in the automation workflow.