What is the typical exception handling convention on the main page of a Blue Prism process?

The typical exception handling convention on the main page of a Blue Prism process involves using an exception block to cover lower layers. This approach enables developers to effectively manage errors and exceptions that may arise during the execution of a process.

By incorporating an exception block, the process can capture any unexpected issues that occur in the underlying stages without impacting the overall performance or flow of the main process. This structured handling ensures that if an exception does occur, it can be dealt with in a controlled manner, allowing for logging, retries, or alternative paths without leaving the main process vulnerable to failures.

Additionally, this method helps maintain the clarity of the process logic. It provides a centralized place for exception handling, making it easier to maintain and troubleshoot the process in the future. In contrast, other approaches such as logging exceptions in every stage or ignoring them could lead to a lack of visibility or a distorted view of the process behavior, complicating maintenance and error analysis.