| Area | Acquia JIRA | Description of functionality after the fix |
|---|---|---|
| Actions | A1DEV-1278 | Improved the performance of the Campaigns listing page when loading a large number of campaigns. |
| Actions | A1DEV-2589 | Fixed an issue where campaigns could fail due to conflicting output column names across different types of content models (e.g. product_name and campaign_name). The system now properly aliases the output headers to ensure there is no conflict. |
| Actions | A1DEV-3481 | Fixed an issue where campaign execution failed when two or more ‘Revenue in a time frame’ calculated content models were added as content to a single campaign. |
| Actions | A1DEV-3504 | Fixed an issue where the Campaign History UI did not refresh the export status to ‘Success’, and instead displayed ‘Running’ after an export. This blocked subsequent exports. |
| Actions | A1DEV-3529 | Added a validation to the UI when content output attributes are empty and Send Now action is performed. |
| Actions Campaigns+ | A1DEV-2913 | Fixed an issue where users were not able to update the ‘Revenue in a time frame’ calculated content model in Segment Criteria. The issue occurred when saving segments built from the segment criteria ‘Revenue in a time frame’ after the segment criteria was named, saved, and renamed. |
| Actions Campaigns+ | A1DEV-3501, A1DEV-4116 | Fixed an issue where Campaigns+ with segments would incorrectly calculate relative time frames (in the last, in the next, in the range of, in the future range of, & at least) in Audience filters/refinements for executions after the first execution. Instead of calculating relative time frames based on the campaign start date time, they were being calculated based on the campaign first execution date time. This has been fixed so that relative time frames are calculated correctly. |
| Facebook Offline Conversions Output Connector | A1DEV-3476 | Fixed the invalid parameter issue due to which Facebook Offline Conversions Output Connector were failing after Facebook introduced the Limited Data Use (LDU) feature: Limiting how data is used for people in California. |
| Privacy API | A1DEV-2932 | Improved the performance of the Privacy API when deleting from campaign history. This should improve the performance of GDPR/CCPA data erasure requests. |
| Responsys Output Connector | A1DEV-4123 | Fixed an issue where the Responsys Output Connector could start to fail after the 2028 release. The issue occurred when there was a mismatch of character-casing (lowercase vs. uppercase) between the Actions Campaign content headers and the Responsys supplemental table. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Fri Sep 12 2025 14:31:48 GMT+0000 (Coordinated Universal Time)