The problem and client impact
An issue has been identified in Pega Customer Decision Hub™ where Treatment changes might not be fully rolled back if Rule generation fails multiple times during an Update Action Change Request. Partially updated Treatment artifacts can remain unintentionally and be promoted across environments, including Production, leading to inconsistent or unexpected Next‑Best‑Action behavior.
Action required
Apply the relevant hotfix specified in the ‘Obtaining your hotfix’ section of this advisory. A restart is not required after applying the hotfix.
Overview
When an Update Action Change Request is used to add a new Treatment to an already deployed Action, Rule generation is triggered. If Rule generation fails more than once, the rollback mechanism might not fully revert all changes. As a result:
-
Portions of the newly added Treatment might remain
-
The Change Request might appear failed, while artifacts persist
-
These residual changes can be promoted to higher environments
-
This might cause inconsistent NBA behavior or build-time errors
How to determine if you are affected ?
You are impacted by this issue if the following factors apply to your application:
-
You use Pega Customer Decision Hub.
-
You use 1:1 Operations Manager.
-
You modify existing deployed Actions.
-
You add new Treatments via Update Action Change Requests.
-
Rule generation fails multiple times, triggering rollback.
If any of the above factors do not apply, no action is required.
| Overview | Description |
| Problem Statement | Stale data present on the OfferDetails page interfered with artifact generation and rollback processing, leading to inconsistent behavior in the Next-Best-Action framework. |
| Impact | Incomplete rollback might leave invalid Treatment artifacts in the Action. This can result in unintended Treatment changes being promoted to production and might cause errors such as “Treatment already exists” during subsequent build operations. |
| Solution |
Apply the relevant hotfix to prevent this issue from occurring. The hotfix ensures that the stale OfferDetails data is removed during artifact generation and revert flows, allowing TreatmentDDR and TreatmentJoinDDR rules to be reverted correctly. |
Obtaining your hotfix
Please review the hotfixes below and take appropriate action. A restart is not required after applying the hotfix.
|
Hotfix |
CDH Version |
|
HFIX-D638 |
25.1.2 |
|
HFIX-D197 |
25.1.1 |
|
HFIX-D618 |
24.2.x |
|
HFIX-D617 |
24.1.x |
If you are a Pega Cloud client, your Pega Cloud® environments are being proactively remediated by Pega. Cloud Maintenance (CM) cases are being created for each of your environments which provides the schedule of when the hotfixes will be applied.
If you are a United States Pega Cloud for Government (PCFG) client, Cloud Change (CC) cases are being created for the hotfix, which will be applied by Pega.
If you are an on–premises or client managed cloud client, please submit a hotfix request using My Support Portal. As always, be sure you have appropriate backups in place before applying the hotfix.