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-209294 · Issue 702711

Support added for variable queue processor partition count

Resolved in Pega Version 8.6.4

An activity called "pxAlterStreamPartitionsInternal" that is defined on Data-Decision-Streamservice- class has been added to support scaling up and scaling down stream service partitions as needed. To allow dataflow runs to automatically detect these changes and redistribute partitions accordingly, a DSS has been added: Owning Ruleset: Pega-DecisionEngine , Purpose: dataflow/run/partitions/changeDetectionFrequency , Value: 120 (default value in seconds) The dynamic system setting may be changed to -1 to disable the automatic partition changes feature, but it is recommended to leave the value set to its configured default. The following articles contain information for executing the activity: https://docs.pega.com/decision-management/87/sizing-queue-processors-and-stream-data-sets-individually-changing-number-partitions-topic https://docs.pega.com/decision-management/87/changing-default-number-partitions-topic Note: The "pxAlterStreamPartitionsInternal" activity is mentioned as "pxAlterStreamPartitions" in the above article, but the steps to execute the activity are the same.

INC-210126 · Issue 708782

Timeout added for Cassandra writes

Resolved in Pega Version 8.6.4

When using Customer Decision Hub with external C* deployment, attempting to stop a data flow run which was reporting stale threads for some partitions resulted in some of the partitions continuing to run while threads were waiting on the Cassandra save operation. This has been resolved by adding configuration for a timeout when waiting for the results of the save operation, with a default of 300 seconds.

INC-210639 · Issue 705347

Query limit removed from Scenario Planner

Resolved in Pega Version 8.6.4

Scenario Planner was not correctly finding or opening some Audience Simulations. Investigation showed that when there are 500+ completed data flows, the system was failing to load next 500 records from pegadata.pr_data_decision_ddf_runtime. This has been resolved by removing the query limits, and additional debug logging has been added.

INC-211251 · Issue 706539

Handling added for Model level Data type empty values

Resolved in Pega Version 8.6.4

After update, the Email Intelligent Virtual Assistant™ (IVA) was not able find the proper response for the real-time incoming emails but was able to find the topic and response when running it from Dev Studio and Prediction Studio. This was due to an edge case where the model datatype page list property was present on the text analyzer rule and a page was present in it, but the property pyName which actually holds the data type (body, attachment, all) was not present in the page. This has been resolved by updating the system to add 'all' as the datatype if the pyName is blank (null or empty).

INC-211349 · Issue 709605

Service API called directly in CDH simulation

Resolved in Pega Version 8.6.4

Running a simulation from the Customer Decision Hub with strategy and dataflow that used customer data resulted in with either a failed run or blank explain detail reports. Investigation showed synchronization was not triggered due to the pxVBDAvailable call returning false, and this has been resolved by directly calling the service API without additional checks.

INC-212169 · Issue 710513

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.6.4

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .

INC-212704 · Issue 707115

Explicit lock release added for Cassandra threads

Resolved in Pega Version 8.6.4

Customer Decision Hub was not responding for realtime request REST service calls, and thread dumps during start up were showing all HTTP request threads were stuck in CassandraSessionCache.getSession. If an error is thrown while invalidating an old Cassandra session, the system may fail to unlock the write lock. This results in subsequent threads being blocked on the session cache's ReadWriteLock when they attempt to retrieve the session from the session cache. To resolve this, an update has been made to ensure that invalidate session is wrapped in a finally block that releases the write lock and log any thrown errors.

INC-212754 · Issue 708688

Log4j file security vulnerability issue addressed

Resolved in Pega Version 8.6.4

A zero-day vulnerability was identified in the Apache Log4j logging software which could potentially allow malicious actors to take control of organizational networks. Pega has immediately and thoroughly addressed this issue. More information can be found at https://docs.pega.com/security-advisory/security-advisory-apache-log4j-zero-day-vulnerability .

INC-213176 · Issue 709974

Data flow stability improvements

Resolved in Pega Version 8.6.4

All nodes were showing as active and running in the cluster, including background, stream, web nodes, but the queue processor would not start. Log entries indicated "IllegalStateException: Invalid run transition found [PENDING_NODES->COMPLETED] on run [DF_OutboundPreProcessing_SMS] by [EventDescription{originator=CheckNodeAvailabilityTask, reason=Restoring previous state." Due to this, all dataflows were moved to queued state. As soon as the corrupted dataflow was deleted the other dataflows were resumed. To resolve this, data flow stability improvements have been added along with better handling of runs in Queued state.

INC-213189 · Issue 707344

Addressed performance issues for classless DSMClipboardPage

Resolved in Pega Version 8.6.4

The DSMClipboardPage implementation handles Page Group access as a classless page (i.e. pxObjClass = ""), creating potential performance issues in implementations where the page group is used with a very large number of distinct AccountIDs in a short period. This has been resolved by updating the system to not cache keys for page group classless page.

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