Should retry loops be nested in Blue Prism?

In Blue Prism, retry loops should not be nested because nesting them can lead to increased complexity in the process logic. When retry loops are nested, managing the flow and the outcomes of each loop becomes challenging, potentially causing confusion and making the process harder to maintain and troubleshoot.

Moreover, nested retry loops can lead to inefficiencies, such as excessive delays or resource consumption if multiple retries are occurring at once. Keeping retry mechanisms simple and straightforward is crucial for ensuring clear and predictable behavior in automated processes. By maintaining a flat structure without nesting, it is easier to understand the process flow and manage exceptions or errors that may occur.

For these reasons, the guidance is to avoid nesting retry loops to promote clarity and efficiency in the automation design.