Executive Summary
Pega has identified a seasonal issue with Customer Decision Hub (CDH) 24.X where campaigns run during December 2026 result in the output file name having the incorrect year (For example: 2027 instead of 2026).
HFIX-D2624 has been released to resolve this problem.
In addition, the issue is fixed in Pega Platform 25.1.3 and 26.1 release
Background: MKTFileNameDateMask DSS in CDH 24.X
Java 7 introduced the uppercase ‘YYYY’ pattern for week-based years in date formatting. In Pega Marketing (Customer Decision Hub), the MKTFileNameDateMask Dynamic System Setting (DSS), uses this pattern to define output file name formats. Since ‘YYYY’ follows the ISO 8601 week-year standard, dates near the end of the calendar year can incorrectly display the next year.
How can I tell if I’m affected?
This defect is a seasonal issue that impacts CDH clients on 24.X and perform campaign runs during December 2026.
|
Hotfix Reference |
Root Cause Analysis |
Customer Impact |
Resolution |
|---|---|---|---|
|
HFIX-D2624
|
Customers relying on file template outputs experienced failures in downstream file processing due to file names containing an incorrect future year value during the end-of-year period.
|
This prevented scheduled communications and other business-critical processes from executing as expected, creating operational disruption and missed engagement opportunities. |
The fix ensures file names use the correct calendar-year format, preventing annual recurrence of the issue and restoring reliable file processing. |
Obtaining your hotfix
If you are a Pega Cloud, or a United States Pega Cloud for Government (PCFG) 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 an on–premises or client managed cloud client, please review the hotfixes to determine which hotfix corresponds to your Pegasystems installation. Once you have determined the appropriate hotfix ID, please submit hotfix requests using My Support Portal. As always, be sure you have appropriate backups in place before applying the hotfixes.