Version 188.8.131.52 Release Notes
Review the fixed features and known limitations in Version 184.108.40.206 for Automation Anywhere Control Room. There are no new features, changed features, or security fixes in this release.
|Zendesk ticket ID or Service Cloud Case ID||Description|
|00497796||The same schedule configured using Schedule management for parent and child tasks now runs only once and not twice for the specified time.|
|00376702||Two threads in the caching service were using the same JDBC statement: one for reading the status of the Ignite cluster and the other for updating the status of the Ignite cluster. Two threads concurrently using the same statement object sometimes resulted in null pointer exception in the Ignite segmentation processor. When this issue occurred, the segmentation processor logic stopped functioning. This issue is now fixed by ensuring each thread uses its own JDBC statement.|
|00363307||Caching service was restarting due to a lost connection between the SQL database and the Control Room node. The connection might be lost due to network connectivity issues, routing issues, or SQL server availability. When the connection was lost, the segmentation processor logic marked the node as segmented. This triggered the Ignite service restart. This issue is fixed by trying to reconnect with the database. If the connection can be reestablished within approximately 7 seconds, the caching service does not restart. In short, this fix applies to short-term database connection losses.|
|--||You can now successfully upload bots without any exception even when the Automation Anywhere Control Room Caching is restarted.|
|00378563, 00373297, 00470918, 00462701||Fixed an invalid partition issue with Apache Ignite in a clustered environment. Communication between the Apache Ignite cache nodes in the Control Room with the clustered setup is resolved. The Control Room installed with any number of nodes now works properly.|
|00437121||Login to the Control Room is no longer delayed if the logged-in user is assigned the locker role (Owner, Manager, and Participant), or queue (Owner or Participant). The system performance is no longer degraded.|
|You cannot directly install the Version 220.127.116.11 patch over the Version 18.104.22.168 and Version 22.214.171.124 patches. If you
try to apply this patch, a warning message appears that
restricts you from installing the Version 126.96.36.199 patch over Version 188.8.131.52 or Version 184.108.40.206 patch. You must
first uninstall your current patch and then install the Version 220.127.116.11 patch.
If you are using the Version 11.3.2 base version, you can directly apply the Version 18.104.22.168 patch.