As described in the previous section on the new load distribution algorithm, the critical limits are the memory consumed by the SAP GUI scripting API that is leveraged within the bot executable. This sections describes how release v2.21 provides additional protection mechanisms to ensure that the bots remain even more stable during the playback.

Key Issues to be solved

Bots are crashing after being overloaded with too many SAP GUI sessions / windows. Even with smart load distribution based upon memory consumption, it is possible that the bots still crash as certain transactions/scripts consume much more memory than others.

Solutions for resolution

There are two new techniques used in v2.21 (described in the following sub-sections) to support achieving this:

  1. Reducing the number of open/active SAP GUI windows during playback
  2. Pausing the bots when they reach a critical memory threshold


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment