Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please update your bookmarks. This site will be discontinued in Dec 2024.

Pega Platform Resolved Issues for 8.1 and newer are now available on the Support Center.

INC-173596 · Issue 660221

Google OAuth and Spring versions updated

Resolved in Pega Version 8.5.6

The Google-oauth-client jar has been upgraded to version 1.31.1, and SpringFramework libraries have been updated to version 5.3.9 .

INC-174661 · Issue 678821

Handling added for clearing node killed between assignment and processing

Resolved in Pega Version 8.5.6

An Offer flow was not resuming after it expired according to the wait shape. Investigation traced this to partitions which were assigned to a dead node in NEW state where they were not picked up by the dataflow. The problem was only encountered in the unusual situation when a dataflow node was killed in the brief period of time between the assignment and the processing, and has been resolved by adding an update which will clear unknown new assigned partitions for the batch run health task.

INC-174781 · Issue 655120

Kerberos authentication added for external Cassandra

Resolved in Pega Version 8.5.6

Support has been added for Kerberos authentication with Cassandra.

INC-175207 · Issue 655553

Added handling for DSM Services stuck in leaving status after database outage

Resolved in Pega Version 8.5.6

During a database outage, the heartbeat would fail and DSM services would eventually try to enter safe mode and stop. As the first step they would try to change the state to LEAVING, but because the database was down saving the LEAVING state failed and the exception was not handled correctly. This resulted in the rest of the stop operation logic not being executed and the service being stuck in LEAVING. To resolve this, an update has been made to ensure the service goes to LEAVING_FAILED if anything fails during the stop operation including when setting state to LEAVING_FAILED. The state LEAVING_FAILED will get flushed to the database eventually when it comes back up. This will allow the aggregation service to start from the LEAVING_FAILED state and recover by itself after a database outage.

INC-177031 · Issue 664856

Adaptive model retry mechanism enabled

Resolved in Pega Version 8.5.6

Adaptive models were missing from the Model Management page as well as in the Prediction studio while similar models for the same proposition, only differing by the Channel name, were visible. This was traced to data not being synchronized between the database and Cassandra. The pegadata.pr_data_adm_factory database table did not contain the record of the missing channel, but Cassandra did. Since the current Cassandra adm_scoringmodel contained model information, the system still believed the model was present. In order to ensure Cassandra and the database table are in sync, an update has been made to enable the retry mechanism "SyncFactoryKeysTask" to create the ADM model in factory table by periodically looking for scoring models without factories or an entry in adm_meta.

INC-179727 · Issue 704546

Modified batch requestor handling to ensure cleanup

Resolved in Pega Version 8.5.6

A large buildup of batch requestors was seen, and restarting the node did not clear it. Investigation showed that in the case of one class reading a DSS value, a Pega requestor was being created when it was unable to retrieve any Pega context, and this requestor was not cleaned up afterwards. To resolve this, an update has been made to the way the requestor and Pega context is being created along with ensuring it will be cleaned up properly after use.

INC-183201 · Issue 667182

Resolved error during save of a Predictive Model

Resolved in Pega Version 8.5.6

Attempting to save a predictive model in Prediction Studio resulted in the error ".pyModelProcess.pyShapes(Setmodelcontrolgroup).pyMOName: Cannot generate the component ID from the provided input. Enter at least one alphabetic character." This was traced to previous work done around defining a control group using a property reference, and has been resolved.

INC-183211 · Issue 667010

Compare-To-Empty-String support added to Analyzer

Resolved in Pega Version 8.5.6

An enhancement has been added to support a NotEquals decision function in the Analyzer.

INC-184352 · Issue 671895

Predictive model snapshot generation updated for Java 11

Resolved in Pega Version 8.5.6

While the Simulation data export case type was executed as expected, the predictive stages showed zero records processed. This was traced to instances running on Java 11 which caused an issue with the snapshot process. This did not affect learning, but visualization and reporting were not working in Prediction studio. To resolve this, an update has been made to the snapshotID for Java 11 compatibility which will generate a random UUID instead of using a seed.

INC-185045 · Issue 672417

Performance improvements for action check-in

Resolved in Pega Version 8.5.6

The process of 'Saving As' an action to a higher ruleset, Saving, and then running Check-in was taking an excessive amount of time. This was traced to redundant page copy activities and performance has been improved by updating the implementation.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us