Summary 

Enhanced order webhook performance by refining database query execution to reduce unnecessary data retrieval and improve response latency. 

Overview 

The order webhook processing logic was updated to remove wildcard (*) column selection in database queries and replace it with explicitly required fields. This change minimizes data load, improves query efficiency, and supports faster webhook execution. 

Additional validation was performed across create, update, and order webhook flows to ensure consistent behavior after the optimization. 

Key Highlights 

Impact 

Improves webhook processing efficiency and reduces latency during order-related events, resulting in faster and more reliable integrations without altering existing functionality. 

Summary 

Enhanced the iframe configuration to include extended membership attributes and streamline the user interface for improved clarity and usability. 

Overview 

As part of the iframe improvements, support was added for extended attributes related to different membership levels. Additionally, the Activity tab was removed to simplify the iframe experience and align it with updated requirements. 

Key Highlights 

Impact 

Provides a cleaner iframe experience while enabling enhanced membership visibility through additional attributes, ensuring better alignment with updated business and UI requirements. 

Summary 

Resolved issues observed during partial returns where campaign capping logic produced inconsistent results in specific configurations, particularly when proportional calculation was disabled. 

Overview 

During validation of partial return scenarios, inconsistencies were identified across APIs and reports for campaigns using capping logic under certain configurations. The behavior was reviewed and aligned to ensure accurate point calculations and data consistency for both discounted and non-discounted return flows. 

Key Highlights 

Impact 

Ensures accurate campaign calculations and reporting during partial return scenarios, preventing inconsistencies during active capping campaigns and maintaining data integrity across customer-facing and internal systems. 

Summary 

Fixed an issue where Tier Report Excel exports contained duplicate member records, which could lead to confusion during reporting and manual analysis. 

Overview 

• When exporting Tier Reports with large data volumes (exceeding 100,000 records), duplicate entries were observed across generated Excel files. This behavior was isolated to the export process and did not affect Tier APIs or dashboard calculations.
• The export batching and file-generation logic has been updated to ensure accurate and non-overlapping data output. 

Key Highlights 

 Impact 

Tier Report exports now generate clean, accurate Excel files without duplicate records, ensuring reliable reporting and confidence in exported tier data. 

Summary 

Reviewed and clarified the behavior of the RAF Access Token flag, which currently disables the RAF iFrame when enabled. A future enhancement will decouple these behaviors to allow API token usage without impacting iFrame visibility.

 Overview 

Key Highlights 

Impact 

Ensures clarity for teams using RAF Access Token functionality, prevents unintended disruption of RAF UI components, and lays groundwork for improved configuration flexibility. 

Summary 

Enhancements were made to ensure RAF email share and congratulations email templates reliably save and display customized HTML content within ADR. This improves template management and consistency for referral-related communications. 

Overview 

Key Highlights 

Impact 

Provides accurate, stable, and customizable referral-related email templates, ensuring a consistent user communication experience across all markets. 

Summary 

This enhancement updates the SSO authentication process to allow seamless login redirection to the new ADR domain using a RelayState parameter, while maintaining compatibility with existing login paths and Microsoft-based direct login flows. 

Overview 

Key Highlights 

Impact 

Enables a smooth transition to the new ADR domain by supporting dual-domain redirection while preserving the stability of all existing authentication processes. 

Summary 

An enhancement has been implemented to prevent approving duplicate receipts in the ADR moderation popup. The system now checks for an existing receipt ID before allowing approval.  

Overview 

Moderators previously had no in-tool visibility into whether a receipt ID had already been processed. This enhancement introduces a real-time validation step in the moderation popup, ensuring that only unique receipt IDs can be approved. 

Key Highlights 

Impact 

Improves accuracy in receipt processing, prevents duplicate point awards, and ensures consistency in the moderation lifecycle. 

Summary 

Fixed an issue where newly added actions with IDs 100 and 106 were not being displayed in the action table, causing incomplete visibility of configured actions. 

Overview 

The system failed to store or surface certain action IDs after creation. This gap resulted in missing entries when validating configured actions. The underlying persistence and retrieval handling was updated to ensure these actions are correctly recorded and reflected in the action table. 

Key Highlights 

Impact 

Ensures accurate visibility of action configurations, preventing misalignment during campaign setup, reporting, or QA validation. 

Summary 

Introduced full support for SMS sending through client-specific Twilio sub-accounts, allowing the users to use its dedicated Twilio credentials and phone numbers without relying on Annex Cloud’s primary Twilio account. 

Overview 

Previously, the SMS service supported only a single Twilio account that was the main Annex Cloud account which prevented clients with their own Twilio sub-accounts from sending SMS through their purchased numbers. This enhancement introduces dynamic credential management, enabling the system to authenticate and send SMS using a client's designated Twilio sub-account when applicable. 
The update includes improvements in validation logic, SMS dispatch workflows, and data handling to ensure backward compatibility with the existing global SMS setup. 

Key Highlights 

Impact 

Enables clients with their own Twilio sub-accounts to send SMS reliably and compliantly through their dedicated numbers, while ensuring all existing SMS functionality continues unchanged for other programs. 

Summary 

Production deployment of updated Single Sign-On (SSO) logic, including support for dynamic SSO URLs and enhancements required for the client’s authentication workflow. 

 Overview 

Key Highlights 

Impact 

Improves the stability and flexibility of the SSO process, ensuring users are redirected correctly and authenticated without errors across environments. 

Summary 

Resolved an issue where member report export had been stuck in processing for more than 24 hours. The export process was analyzed and corrected, and the report was successfully retrieved and shared. 

Overview 

Key Highlights 

Impact 

Ensures that member report export jobs complete reliably and prevents extended delays that may affect operations or reporting schedules. 

Summary 

A new enhancement was introduced to automatically enroll members into the VIP tier based on the generateSubscription parameter received from the store. The enhancement applies to both newly created and existing loyalty members, supporting seamless subscription and re-subscription to VIP membership. 

 Overview 

Key Highlights 

 Impact 

This enhancement ensures accurate real-time tier alignment between the store’s subscription state and AC’s loyalty system, providing a seamless and consistent VIP membership experience. 

Summary 

A correction was implemented to address a case where points shown as awarded in /bulkpatchorder API responses were not being credited to members. This impacted retroactive adjustments submitted to correct missed hours due to an external system issue. 

Overview 

Key Highlights 

Impact 

This fix restores accurate loyalty accounting for retroactive adjustments and prevents inconsistencies between expected and actual point awards. The update ensures historical corrections function reliably and are reflected immediately in the loyalty system. 

Summary: 
Resolved an issue where the User Action Status API returned incorrect paginated results, causing action records to appear duplicated on multiple pages while valid actions were missing entirely. 

Overview: 
During pagination of the Action API response, certain actions with identical ordering values appeared on more than one page, and some eligible actions were not returned at all. The underlying query relied on a non-unique sort field, which caused non-deterministic pagination. The logic has now been updated to ensure consistent ordering and correct page-wise distribution of action records. 

Key Highlights: 

Impact: 
Ensures the User Action Status API returns accurate, complete, and consistently paginated results, preventing missing action records and duplicate listings. 

Summary: 
Implemented trimming logic for product_id, category_id, and applicable segment condition fields to ensure accurate matching and consistent behavior during segmentation processes. 

Overview: 
Whitespace inconsistencies in product and category identifiers caused mismatches during segment evaluation. Updated logic now trims these fields before processing, improving accuracy across segmentation workflows and related campaign use cases. 

Key Highlights: 

Impact: 
Ensures precise ID matching, prevents missed segment qualifications due to formatting variances, and stabilizes downstream campaign execution. 

Summary: 
Corrected the behavior where campaigns were not being applied to orders submitted with a SHIP status in the issuance create API. 

Overview: 
When an order was created directly with the SHIP status, the campaign evaluation process did not trigger as expected. The campaign-application logic has been updated so that SHIP-status orders are processed consistently with other eligible order statuses. 

Key Highlights: 

Impact: 
Ensures campaigns are accurately applied for orders passed directly with SHIP status during issuance creation, supporting consistent loyalty earning logic across order flows.

Summary: 
Updated the Full Cancel Issuance API to ensure the expected response structure is returned during affiliate cancellation processing. 

Overview: 
In the full-cancel flow, ProductDetails was being returned as a single object, while the receiving system requires a list of objects. The response construction logic was updated to maintain consistent formatting across both full-cancel and partial-cancel scenarios. 

Key Highlights: 

Impact: 
Ensures smooth processing of affiliate cancellation requests and consistent interoperability with connected systems. 

Impact: 
Improves performance, stability, and consistency across review and solicitation workflows, ensuring accurate functionality for all dependent product areas. 

Key Highlights: 

Impact: 
Ensures accurate and properly formatted referral status information for Spanish-language users, improving clarity and consistency across multilingual RAF experiences. 

Summary: 
Resolved an issue where long product IDs uploaded through Excel were being altered due to automatic numerical formatting, resulting in incorrect values being stored and used in segment and campaign conditions. 

Overview: 
When uploading product IDs via Excel, any ID containing 12 or more digits was being auto-converted and rounded by Excel before the system processed the file. This caused product IDs to be stored in an incorrect format, impacting eligibility checks for segments and campaigns tied to those product IDs. 

Example behavior before the fix: 

Manual entry of product IDs worked correctly, confirming the issue was specific to Excel-based uploads. 

Key Highlights: 

Impact: 
Guarantees accurate product ID storage for all Excel-based uploads, ensuring campaigns dependent on product-level conditions behave consistently. 

Summary: 
Resolved an issue where bonus point entries generated by campaign activity were not appearing in the campaign_benefit table, resulting in incomplete data visibility during validation. 

Overview: 
Bonus point entries associated with a specific campaign were not being recorded as expected. The underlying logic responsible for persisting campaign bonus details was updated and validated to ensure accurate entry creation. 

Key Highlights: 

Impact: 
Ensures accurate tracking and availability of campaign bonus point records for downstream reporting and verification. 

Summary: 
Resolved an issue where actions without a configured expiration date were incorrectly displaying an expiration value of 01-01-1970 in the Activity section of the reward dashboard. 

Overview: 
Actions that do not have an expiration date defined were being assigned a default UNIX epoch date, leading to misleading information in the activity view. This occurred when creating or updating activities via API for existing customers. 
The update ensures the expiration field remains accurate and does not show placeholder dates for such actions. 

Key Highlights: 

Impact: 
Ensures accurate and clear activity details for users, preventing confusion caused by incorrect expiration dates. 

Summary: 
Resolved an issue where members could go into a negative points balance after multiple partial refunds when proportional calculation and partial refund logic were enabled. 

Overview: 
A member performing sequential partial refunds on an order experienced an incorrect points deduction. 
Although the “Do Not Allow Negative Points” setting was enabled, the system deducted the full expected points for the second partial refund instead of capping the deduction at the member’s available balance. 
This caused the account to drop below zero. 

The fix updates the refund deduction logic to ensure that when proportional calculation and partial refund handling are active, the deduction never exceeds the member’s current point balance. 

Example Scenario: 

A secondary scenario involving an unexpected deduction value during a single-item refund was also addressed as part of the update. 

Key Highlights: 

Impact: 
Prevents negative point balances during multi-step refund workflows and ensures accurate, predictable point deductions in proportional refund scenarios. 

Summary: 
Developed a dedicated API endpoint for the 2025 Holiday Promo campaign to enable seamless promo code validation and redemption using the unique code HAPPYHOLIDAYS2025. 

Overview: 
A new API was implemented to manage promo code validation and redemption for the 2025 Holiday campaign. 
The endpoint ensures proper handling of promo logic and accurate association with campaign actions. 

The solution provides automated validation for promo eligibility and supports efficient redemption management. 

Key Highlights: 

Impact: 
Improves campaign execution by automating promo validation and ensuring accurate reward distribution for eligible users. 

Summary: 
Resolved an issue where key user details and custom attribute values were not being reflected in PostgreSQL for multiple sites. 

Overview: 
It was observed that user information—specifically phone number, zipcode, source, and birth_date—was showing as null in PostgreSQL, despite being available in the Member Report. Additionally, all custom attribute parameters were missing from the user table. 

The issue occurred due to gaps in the synchronization logic between the user creation API and PostgreSQL data mapping, which caused selective column values to fail during sync. 

The logic has been corrected to ensure that all user details and custom attributes are now accurately inserted and updated in PostgreSQL during user creation and modification processes. 

Key Highlights: 

Impact: 
Ensures complete and accurate user data representation across databases, improving consistency between application data and PostgreSQL for downstream analytics and reporting. 

Summary: 
Resolved an issue where milestone entries were not being recorded in PostgreSQL after an order was created and a campaign with milestones was applied. 

Overview: 
During testing, it was identified that milestone-related data failed to sync to PostgreSQL even though the campaign was successfully applied to the order. The missing milestone entry caused inconsistencies between the campaign tracking data and the database records.   

The issue occurred due to a missing mapping in the milestone data synchronization logic within the campaign benefit process. This prevented milestone records from being inserted into the corresponding PostgreSQL tables. 

The sync logic was updated to ensure milestone entries are now correctly captured and reflected in PostgreSQL whenever an order triggers a milestone campaign. 

Key Highlights: 

Impact: 
Ensures all milestone data is accurately stored and tracked in PostgreSQL, improving data integrity for campaign reporting and milestone-based reward calculations. 

Summary: 
Standardized PostgreSQL data synchronization logic to correctly handle data types across all API payloads, replacing empty strings with null values where applicable. 

Overview: 
The issue was identified in multiple sync APIs where string, integer, and decimal fields were inconsistently handled — particularly when empty strings ("") were passed instead of null or type-appropriate values. This led to data mismatches and type conflicts in PostgreSQL. 

To address this, data type enforcement and validation were implemented across all PHP sync modules. Each payload now adheres to proper typecasting rules to ensure database consistency and data integrity. 

Key Highlights: 

Impact: 
Prevents data type mismatches and errors in PostgreSQL sync processes, ensuring accurate and reliable data migration and integration across systems. 

Summary: 
Resolved an issue where multiple campaigns were not being applied when the Multiple Campaign Benefit flag was enabled and store-specific configurations were used in the issuance purchase process. 

Overview: 
When the Multiple Campaign Benefit flag was turned ON, campaigns that had store-based applicability were not being triggered correctly. The root cause was traced to a validation gap in the store ID filtering logic, which caused applicable campaigns to be skipped when multiple store IDs were passed. 

The logic was refined to ensure all eligible campaigns are correctly identified and applied, even when store-level filters are active. 

Key Highlights: 

Impact: 
Ensures consistent application of multiple campaigns for eligible purchases, improving reward accuracy and campaign reliability. 

Summary: 
Prepared for the migration of the loyalty program iFrame from Tiers v1 to Tiers v2, ensuring compatibility with updated tier configuration logic ahead of the planned rollout in 2026. 

Overview: 
The update focused on aligning the existing iFrame and backend systems with Tiers v2 capabilities, as the new tier configuration will operate on a Calendar Year–based model. All supported parameters under Tiers v2 were implemented, while unsupported fields from Tiers v1 were deprecated to maintain consistency and improve data handling.  

The migration also included ensuring backend synchronization with ADR data sources and integration systems, such as reporting modules and third-party connectors. 

Supported Parameters in Tiers v2: 

Not Supported in Tiers v2: 

Key Highlights: 

Impact: 
Facilitates a seamless transition to Tiers v2 with accurate iFrame data display, consistent reporting, and enhanced performance reliability across systems. 

Summary: 
Updated the S3 bucket configuration for RNR AJAX image uploads to use a new region-specific bucket in the AWS AP region. 

Overview: 

Key Highlights: 

Impact: 

Summary: 
Developed and validated multiple Order and Points API balance summary scenarios to ensure accurate and consistent balance updates during concurrent and normal operations. 

Overview: 

Key Highlights: 

Impact: 

Summary: 
Enhanced the point expiration calculation logic to support scenarios where the Allow Negative Point Balance flag is enabled, ensuring accurate point settlement for both standard and negative balance cases. 

Overview: 

Key Highlights: 

Impact: 

Summary: 
Resolved an issue in the Interaction Report where the selected date range automatically changed when the user clicked the search button multiple times. 

Overview: 

Key Highlights: 

Impact: 

Summary: 
Introduced product changes in the RAF PPC flow to block Mandrill service calls during email sharing. 

Key Highlights: 

Impact: 

Summary: 
Resolved an issue where referral emails were not being sent correctly when multiple email addresses were entered in the share text box. Previously, only the first email address received the invite, while subsequent addresses were ignored. Additionally, the system displayed a persistent loading screen after submission. 

Overview: 

Key Highlights: 

Impact: 

Summary: 
Resolved an issue where user data was not being pushed to the ESP account every 5 minutes due to tier parameter field mapping errors. 

Overview: 

Key Highlights: 

Impact: 

Summary: 
Fixed an issue where receipt approvals were failing and causing the system to freeze, preventing moderators from approving receipts. 

Overview: 
When attempting to approve receipts, the system displayed a loading icon without completing the approval process. The issue was identified as template-specific, with some templates functioning correctly while others consistently failed. Additional issues included receipts remaining in “Pending” status after rejection and duplicate entries appearing in the product selection dropdown. 

Key Highlights: 

Impact: 

Summary: 
Implemented major performance enhancements to the Member Report Export process, reducing database load and significantly improving batch and Excel preparation speed. 

Overview: 
The Member Report Export previously relied on per-row SQL queries, leading to excessive database calls, slow performance, and scalability issues. The process has been restructured to preload required data into maps, use batched queries, and centralize date formatting logic. This ensures faster execution and more efficient memory usage for large datasets. 

Key Highlights: 

Impact: 

Summary: 
Enhanced the TierV2 Scheduled job process to improve logic for migrating users from TierV1 to TierV2, ensuring smoother and more accurate tier transitions. 

Overview: 
The existing TierV2 Scheduled job logic has been updated to handle user migration from the older TierV1 system to TierV2. These improvements focus on ensuring consistent and accurate tier assignment, reducing errors during automated migrations, and streamlining the transition process for all members. 

Key Highlights: 

Impact: 

Summary: 
Fixed an issue where campaigns were incorrectly becoming eligible when the Exclude Category ID was passed as blank during order placement. 

Overview: 
The defect caused campaigns configured with an excluded category to still be applied if the order payload included a blank category ID. This led to incorrect campaign eligibility being granted to users.  

Key Highlights: 

Impact: 

Summary: 
Resolved an issue where the Tier Report export did not display all eligible members when filters were applied, leading to discrepancies between the admin view and the exported file. 

Overview: 
When applying tier filters to generate the export, certain members who met the criteria were not included in the output file. Investigation revealed that the filter logic in the export process was not aligned with the admin Tier Report display logic. This caused inconsistencies in member visibility between the admin report and the exported data. 

Key Highlights: 

Impact: 
Provides accurate and complete Tier Report exports, ensuring consistency with the admin view and reliability in data usage for reporting and analysis. 

Summary: 
Enhanced the Journey API to support translations for journey names, descriptions, and future attributes, enabling multi-language compatibility through the existing API translation framework. 

Overview: 
Previously, Journey endpoints lacked translation support, restricting their usability in multilingual environments. This enhancement extends the API to handle translatable attributes, ensuring that journey-related information can be localized effectively. Development tasks included grooming, ADR changes, and adding support for custom language codes in loyalty APIs. Testing and rollout are aligned with release schedules to meet customer requirements. 

Key Highlights: 

Impact: 

Summary: 
Resolved an inconsistency where a member’s Opt-In date displayed differently between the Member Report screen and the Member Dashboard edit view. 

Overview: 
The Opt-In date for members was not aligned across reporting and dashboard edit screens, causing confusion in data interpretation. The fix ensures that both locations now reflect the same, correct Opt-In information. This update also aligns date and time handling across multi-template and non-multi-template sites for better consistency. 

Key Highlights: 

Impact: 
Ensures accurate and consistent Opt-In information across all member views, improving data reliability and supporting smoother campaign and reporting workflows. 

Summary: 
Resolved the issue where Issuance Order Details Reports requested were not being processed or delivered. 

Overview: 
The report generation system failed to process and send requested Issuance Order Details Reports, causing delays in accessing critical data. The fix ensures reliable processing and delivery of these reports. 

Key Highlights: 

Impact: 
Ensures timely and accurate delivery of Issuance Order Details Reports, restoring trust and enabling stakeholders to review and act on critical data without disruption. 

Impact: 
Strengthens data consistency and reliability across integrations, enabling accurate synchronization and improved downstream processing. 

Summary:

Fixed an issue where dashboard reports generated in the multi-template reporting view displayed no data. 

Overview:

The dashboard reporting functionality was not designed to aggregate data across multiple templates. When users attempted to generate a dashboard from the multi-template reporting view, the result was an empty report with zero data. This caused confusion for users expecting aggregated results. To resolve this, the dashboard option has been disabled for multi-template reports, while retaining full functionality for individual template-specific reports. 

Key Highlights:  

Impact 

Summary:

Fixed an issue where the coupon group UI on the Additional Loyalty Settings page was not visible due to excessive reward codes. 

Overview:

The coupon group UI failed to load when handling a very large dataset of reward codes, making it inaccessible to users. To resolve this, performance improvements were implemented along with a loader indicator to show progress while the UI loads. With this fix, the coupon group UI now displays correctly and remains functional under heavy data loads. 

Key Highlights: 

Impact: 

Summary:

Resolved an issue where, in an order, if two campaigns were applied, points from the second campaign were not being added to the total points calculation. 

Overview: 
Earlier, when two campaigns were applied to an order, the second campaign was correctly tagged to the product, but its points were excluded from the total points calculation. This happened because the limit of the first campaign was incorrectly applied to both campaigns. With this fix, points from both campaigns are now calculated independently, ensuring members receive the full benefit as configured. 

Key Highlights: 

Summary:

Fixed an issue where the Reward Report did not display Order IDs for used vouchers, even though the Order Report captured them correctly. 

Overview:

Previously, when multiple vouchers were applied to the same order, the system correctly updated their status from “Claimed” to “Used”. However, in the Reward Report, the corresponding Order ID was not being displayed against these used vouchers. This bug has now been resolved, and the Reward Report properly shows the Order ID for each used voucher. 

Key Highlights: 

Impact: 

Summary:

Improved validation for email addresses in Order API to ensure loyalty points are awarded even if the email format is non-standard. 

Overview:

Previously, when loyalty members placed an order via the Order API with a non-standard email address format, the system threw an error and failed to award points. With this enhancement, the validation logic has been updated to accept all email address formats, ensuring that members continue to receive their loyalty points regardless of email formatting. 

Key Highlights: 

Impact: 

Summary:

Users can now manually enter new fields during field mapping, in addition to selecting from the available field options. 

Overview: Earlier, while creating a new integration, users could only select from the predefined list of available fields during field mapping. With this enhancement, users have the flexibility to add and map custom fields manually, apart from the existing options. This improves adaptability for diverse integration requirements. 

Key Highlights: 

Impact: 

Summary:

A loader has been added to the log records search functionality. 

Overview:

In the Integration Dashboard log records search page, there was no loader previously. When users searched for log records by providing a date range, the system would begin processing the request, but users had no indication whether the search was in progress. With this enhancement, a loader now appears when a date range is entered, and a search is initiated. This provides a clear indication that the system is actively searching for records. 

Key Highlights: 

Impact: 

Summary:

Pagination in the ESP log page has been limited to 5 records per page. 

Overview:

Previously, when searching for log records in the ESP log page, the system displayed more than 5 records on a single page. This caused the table to extend beyond the defined page setup, making it difficult to view and navigate through all records. With this bug fix, pagination is now limited to 5 records per page. Users can navigate to the next page to view additional records until all records are displayed. 

Key Highlights: 

Impact: 

Summary:

Introduced a group-level points limit in the Advance HM system to ensure actions consider both individual and group credit limits for accurate points management. 

Overview:

This enhancement adds logic to enforce points limits when members belong to a group within Advance HM. The update ensures that both group-level and user-level limits are respected during points allocation.  

Key Highlights: 

Impact: 

Summary: 
Resolved an issue in the Group Points Expiration API where the points shown as pending expiration did not match the actual points deducted after the scheduled job execution.

Overview: 
This issue occurred due to a mismatch between the points calculation logic in the Group Points Expiration API and the actual expiration process during scheduled jobs. The logic was corrected to ensure that the points shown in the expiration API match the final points expired after the job runs. Testing confirmed accuracy across both calendar-based and rolling expiration configurations. 
 

Key Highlights: 

Impact: 

Summary: 
Updated the segment eligibility logic for excluded stores to ensure that orders without store information are correctly processed for campaigns.
 

Overview: 
Previously, if an order did not contain a storeId key or had a blank storeId value, it was automatically marked ineligible for segments with excluded stores. This caused web orders (which often omit store details) to miss campaign benefits despite meeting other criteria. The enhancement ensures that such orders are treated as eligible unless they explicitly contain an excluded store ID. 

Key Highlights: 

Impact: 

Summary: 
Updated the campaign and segment configuration UI to display both the Action ID and the Action Name/description in dropdowns and filters. This helps in accurately identifying the correct Action when multiple actions have similar descriptions.
 

Key Highlights: 

Impact: 

Summary: 
Fixed an issue where the Group Points Expiration API displayed a lower points-to-expire value before expiration, but a higher number of points expired after the points expiry job execution. 
 

Overview: 
In certain scenarios involving both Calendar-based and Rolling-based point expirations, the Group Points Expiration API would show an incorrect value prior to expiration. For example, the API displayed 90 points as due to expire, but after scheduled job execution, 100 points were expired. This misalignment caused inconsistencies between pre-expiration data and post-expiration results. 
 

Key Highlights: 

Impact: 

Summary: 
Resolved an issue where concurrent (multi-threaded) calls to the Assign Badge API caused incorrect updates to the badge summary table. 

Overview: 
Previously, when multiple calls to the Assign Badge API were processed simultaneously, race conditions could result in inaccurate summary data. The update logic has been revised to ensure atomic and consistent updates regardless of the number of concurrent requests. 

Key Highlights: 

Impact: 

Summary: 
Fixed an issue where the wrong error message was displayed when an invalid value was provided for the member_reward_status filter in the GET eligibility API. 

Overview: 
When users passed an unsupported value for the member_reward_status filter, the API returned an incorrect error message referencing unrelated status values (Draft, Scheduled, Live, Archived). The logic has been updated to return a precise error message specific to the allowed values for member_reward_status. 

Key Highlights: 

Impact: 

Summary: 
Resolved an issue where group details were not being removed when selecting “Select” from the dropdown, particularly for groups that had descriptions. 

Overview: 
The system failed to clear group details after update operations when a group with an associated description was deselected. This caused outdated group information to persist, leading to inconsistencies in group assignments. 

Key Highlights: 

Impact: 

Summary: 
Resolved an issue where coupon groups were not immediately visible or took longer to appear during initial page access. 

Overview: 
Enhancements were made to the Coupon Group UI to ensure prompt visibility and faster loading of groups. The update improves responsiveness while maintaining all existing coupon distribution functionality. 

Key Highlights: 

Impact: 

Summary: 
Fixed an issue where the Get Action Status by User API returned duplicate entries for the same Action ID, ensuring each Action ID is now returned only once in the response. 

Overview: 
The Get Action Status by User API was updated to resolve a duplication issue caused by the POST method logic. This fix ensures the API returns a single, accurate record per Action ID, improving data consistency across systems. 

Key Highlights: 

Impact: 

Summary: 
Resolved bulk upload failures where user records were not consistently pushed to ESP accounts during scheduled jobs, especially for uploads exceeding 2,000 users. 

Overview: 
Testing revealed that bulk uploads at various job frequencies were partially successful for smaller batches but failed or pushed incomplete data for larger volumes. Failures were linked to ESP rate limits, timeouts, and cron job execution issues. Code optimizations and retry-after handling were implemented, improving push rates in most scenarios. Related tickets were created for specific ESP/frequency issues, with the functionality now ready for targeted retesting. 

Key Highlights: 

Impact: