An application being automated is prone to respond slowly when there is a lot of...

Understanding the Scenario:

The application being automated is prone to respond slowly due to network traffic.

The automation needs to handle these latency issues efficiently.

Evaluating the Options:

Option A: An Unconditional Wait (Throttle) is not an optimal solution as it does not adapt to varying response times and can unnecessarily slow down the automation.

Option B: Using a block and recovery with a retry loop is complex and not the best approach for handling expected latency issues. This is better suited for handling unexpected errors.

Option C: Adding a Sleep stage before a Conditional Wait stage is not efficient as it adds unnecessary wait time before checking the condition.

Option D: A Conditional Wait stage with a Global Timeout is the best approach. It allows the automation to wait for a condition to be met (e.g., an element to appear) with a maximum wait time that accommodates system latency. This method is adaptive and efficient.

Conclusion:

The best way to manage performance issues due to slow responses is to use D. Use a Conditional Wait stage with a Global Timeout value which is sufficient to accommodate the system latency.

References:

Blue Prism Developer Documentation: Wait Stages and Performance Optimization

Blue Prism Training Material on Handling System Latency