If a process in Blue Prism continues to experience the same exception frequently, what is the recommended action?

When a process in Blue Prism is consistently encountering the same exception, it indicates a recurring issue that needs attention. It is crucial to address these repetitive exceptions to ensure the reliability and efficiency of the automation.

The recommended action in such cases is to terminate the process after counting occurrences. This approach allows for monitoring the frequency of the exception, providing valuable data on the severity and potential impact of the issue. Tracking these occurrences can help identify underlying problems, enabling the team to diagnose and resolve the exception more effectively. By terminating the process, it prevents further attempts that may lead to unnecessary resource consumption or additional complications.

Counting occurrences before termination can also aid in understanding patterns or trends related to the exceptions, which can inform future improvements or adjustments to the automated processes. This step ensures that the root cause is analyzed and addressed, rather than merely applying a temporary fix or allowing the process to run unchecked.