Known Limitations and Operational Constraints

This chapter summarises the known product limitations that directly affect L2 day-to-day operations. L2 must be aware of these constraints so that they can set correct expectations with stakeholders, avoid incorrect escalation paths, and operate within the boundaries defined by the engineering and product teams. For more information, refer to the HCL MaxAI Canonical Release Notes.

Carry-Forward Limitations from Release 25.1

The following limitations were introduced in Release 25.1 and remain active in Release 26.1. L2 must not attempt workarounds outside of documented runbooks for these items.

Issue ID Description
HMA-402691

HCL MaxAI CDM currently does not support data insights from below Unica product components:

  • Event-level and journey-level interactions
  • Offer-level analytics

Workaround: Use existing Unica product-specific reports and analytics for detailed event, journey, and offer-level insights.
HMA-402699 Formal reconciliation and audit frameworks are not included in the current release.

Workaround: Perform manual reconciliation and auditing using external governance processes and reporting tools.
HMA-402701 Detail Contact history( UA_DtlContactHist) is not considered for creating Campaign 360.

Workaround: Use summary-level campaign history data for Campaign 360 analysis.
HMA-402704 Retention and archival policies are not implemented in the pipelines and will be formalized in future releases.

Workaround: Manage retention and archival externally using database-level or enterprise data governance policies.
HMA-402706

Detailed performance tuning guidelines and data model optimization recommendations for each supported database will be made available to help optimize performance based on chosen database Very high-volume datasets may require additional Oracle tuning.

Workaround: Apply Oracle database performance tuning and optimization based on deployment scale.
HMA-411412 Deleted treatment should be scoped out from the calculations of matrixExecution count should consider only records with treatment code.

Workaround: Apply filtering logic manually to include only records with valid treatment codes.
HMA-412651/HMA-412652 ML ops features will support the account and device level audiences as well

Workaround: Use existing audience segmentation capabilities or manually configure account/device-level audience mappings until ML Ops support is available.