SR-D36591 · Issue 507537
Kafka producer message size made configurable
Resolved in Pega Version 8.2.4
Kafka producer was using a default max message size setting of 1.3Mb while the Kafka broker max message size was set to 5Mb. This caused large processing queues to eventually throw errors indicating a scheduler.JobExecutionException related to "There was a problem saving an instance of class System-Message-QueueProcessor-DelayedItem". To correct this, a producer message size configuration option has been added along with additional logging for the KafkaSaveOperation.
INC-178214 · Issue 664890
D_ProjectList updated to resolve defined databases error
Resolved in Pega Version 8.7
After update, an API error for D_ProjectList indicating "No databases defined" was seen when trying to load decision and templates for the first time. The error did not reoccur after the initial save. This was has been resolved by updating the handling for loading the properties file during class loading. The error has also been changed to an exception.
SR-D53225 · Issue 516316
Rule creation logic updated to include creation branch
Resolved in Pega Version 8.3.2
When trying to create a new adaptive model rule in Prediction Studio, the “Create” button was not activating. The adaptive model rule was being saved in a branch ruleset, and investigation indicated that the deactivated button could be traced to the lack of an open ruleset version available even though the intention was to create it on a branch. This has been resolved by modifying the rule creation logic to incorporate the branch for creation.
INC-182137 · Issue 662488
Multistage Prediction Logic improved
Resolved in Pega Version 8.7
When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.
INC-188124 · Issue 672587
Multistage Prediction Logic improved
Resolved in Pega Version 8.7
When Predictions with Response wait time configured were executed as part of make decision, each decision that came out of the strategy caused a pxDR call to fetch the relevant model execution results and process them to stage the default outcome results for models. This has been improved by modifying the system to process the existing records rather than reading data again from pxDR.
SR-D31103 · Issue 502978
VBD insert process updated for better retry handling
Resolved in Pega Version 8.2.4
When restarting Data Flow and VBD nodes, the VBD client can encounter some exceptions indicating components in the stack are temporarily unavailable. In most cases the VBD client retries, but there are some cases where it did not and data flow failures occurred. To resolve this, the code has been updated to remove logging of the VBD cluster status during a retry, and the retry duration has been made configurable.
SR-D38415 · Issue 507995
Resolved Transfer to Queue duplicate assignments
Resolved in Pega Version 8.2.4
The Transfer to a Queue option was creating duplicate assignments after accepting the Chat. Once the chat was accepted, an instance was created\maintained in both Assign-Workbasket and Assign-Worklist tables. This happened after adding the "Transfers" queue to an Agent; if that queue was not added, the transfer to a queue option gave an error to the Agent receiving\accepting the chat. The Work-.ReassignDefaults activity is an extension that was customized in the Pega-DecisionManager ruleset for a certain use case in revision management. The customization is no longer required and has become redundant and has therefore been removed to resolve this issue.
INC-174661 · Issue 678822
Handling added for clearing node killed between assignment and processing
Resolved in Pega Version 8.7
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.
SR-D74117 · Issue 539460
DDS service will not run Hazelcast check if external Cassandra is configured
Resolved in Pega Version 8.3.2
Services were not responding, and thread dumps seen in the logs indicated that a large number of threads were waiting for one to come back from getting the cluster state for a DSM process. Investigation showed that the threads were waiting for a Hazelcast response about the cluster state. However, since a Hazelcast call is not needed when Pega is configured with external Cassandra, the DDS Service code has been changed to not to check for candidate nodes if configured with external Cassandra cluster.
SR-D79909 · Issue 542243
DDS added for automated dataflow run cleanup
Resolved in Pega Version 8.3.2
During a recent upgrade it was seen that there were in excess of 20k dataflow runs, some 2 years old, which slowed down the migration significantly. In order to resolve this, an automated process has been added. This clean-up procedure deletes all the single case, batch, and real time runs older than 30 days which are in the final state - Completed, Completed with Failures, or Failed, and batch and real time runs which are in the Stopped state. The DDS Pega-DecisionEngine.dataflow/run/maxDaysToKeepRuns.should be used configure the retention period. Note that the retention period is calculated since the last processed message and not the creation time of the run.