Known limitations

The following table lists known limitations in Interact 9.1.1.

Issue Number Description

Null pointer exception while saving strategy containing large number of treatment rules created by rule wizard


If you create approximately 900 rules by adding one offer and 900 segments with the rule wizard and try to save the strategy, the following error is displayed.

Interact deployment rollback is not supported with Advanced Patterns (time bound and rolling time)


V1 is not synchronized in Advanced Patter run time if you perform the following workflow.
  1. Create an interactive channel that contains only simple pattern and deploy this version V1 to the Interact run time.
  2. Add an advanced pattern counter (time bound) type of pattern in interactive channel and use the same in interactive flowchart to populate segment that is based on pattern state.
  3. Deploy this interactive channel to runtime and version V2 is created. The same is reflected in the Detect workspace.
  4. Rollback or redeploy to version V1. After redeploy is successfully complete, the Opportunity Detect workspace shows version V2.

A persistent derived field is not profiled in a downstream Decision process in an interactive flowchart.


If you create a persistent derived field in a flowchart process, then connect the output of that process to a decision process to try to profile the persistent derived field, the field is not profiled.

To workaround this issue, profile the original derived field.

Offers in treatment rules do not appear in Interact report


If you do not select offers created with an offer template with Allow offers created from this template to be used in real-time interactions selected, Interact cannot collect the correct data for reporting.

Test run result tables are not dropped from Interact test run tables


When you run a test of an interactive flowchart, Interact creates four tables in your test run tables for each interactive flowchart. These tables are not deleted if you delete the interactive flowchart.

SOAP client does not release threads


The SOAP client leaves sockets in a CLOSE_WAIT state instead of closing them. This is a known issue with the Axis2 SOAP client. See for details.

Cannot stop an interactive flowchart test run


You cannot stop or pause an interactive flowchart test run. Test runs are designed to run on a subset of data, for example hundreds of rows. You can configure the size of your test run in the Interaction process. See the HCL® Interact User's Guide for details.

Interact interactive flowcharts support a subset of Campaign macros.

DEF057366, ENH11494

By design, interactive flowcharts support (and make available for selection) only a subset of the macros available on batch flowcharts. On an interactive flowchart, in any Select or decision process boxes where you want to use a macro that is not supported (for example, the between operator, as in "AGE between 1 and 18"), an error message "Function or operation not supported" appears when you check the syntax. This is expected behavior.

Test run does not change value of user variables in design time


If you perform a test run of an interactive flowchart that contains a user variable, the value of the variable does not change in the design environment (HCL Campaign). In runtime, you can use a session name-value pair to view the user variable current value.

Distributed caching in hybrid architecture is not supported


Interact does not support distributed caching in architectures that use a combination of operating systems on different instances of the runtime environment (for example, an instance on UNIX™ with Oracle and an instance on Windows™ with SQL Server). To support various components, including ETL capabilities, Interact requires that all instances of the runtime environment be of the same operating system type.

Raw SQL options are not supported in Interact flowcharts


Using custom macros with expression type "Raw SQL Selecting ID List" or "Raw SQL Selecting ID List+Value" in any processes in an interactive flowchart results in Error 11324.

Known limitation with German character szlig


The German Eszett character szlig (Unicode U+00DF) is not supported in Interact.

  • Interact initialization fails when an Audience is mapped to a table that contains this character.
  • An eligible Segment name that contains the character displays incorrectly when the segment is added to an interaction strategy.

UACI_EligStat table logs offers with effective dates that should have been excluded by effDateBehavior>


Offers with effective dates that falls out of the (effectiveDateBehavior + effectiveDateGracePeriodOfferAttr) are being logged as eligible offers in the UACI_EligStat table. The parameter specified in effectiveDateGracePeriodOfferAttr is not dynamic therefore if you include a "Grace_Period" attribute in effectiveDateGracePeriodOfferAttr and this is included in offers, every time the value for this parameter is changed in the offer, it requires redeployment of the interactive channel.

Constraint state and in-memory caches are lost on restarting Interact runtime server.


If the Interact runtime server is restarted for any reason, the most recent constraint state (stored in memory, for performance reasons) and any in-memory cache data is lost.

Offer constraints do not work as expected when multiple offer constraint rules are added in one interactive channel for same set of offers.


Interact currently does not support multiple constraints to be applied independently over different intervals of time for a specific deployment. Offers that fall under multiple constraints will follow the most restrictive of the constraints.

Modifying constraint parameters (such as start date or maximum number of offers per interval) results in changes to how the offers are served using that constraint.

DEF057070, DEF057076

Modifying the settings may affect constraint results in several ways:

  • Changing the start date of an offer constraint midstream may result in the counter being reset to zero. This occurs because when the startTime changes, the interval is recalculated and may yield a different interval, so the count may be reset.
  • On the Interact Constraint State page, the Current count for this interval data does not update if you change the offer constraint's start date to an earlier date. This issue occurs because, when the start time is changed, the interval must also be recalculated. The constraint state is updated correctly after that initial recalculation.

For more information about how the constraint parameters affect the outcome, see the HCL Interact User's Guide.

When issuing the getoffersForMultipleInteractionPoints call in the Interact API, the top-level attribute requirements can accept at most one attribute.


For example, if you set up offers in an Interactive Channel and execute a getoffersForMultipleInteractionPoints() API call using the Offer Attribute with OfferType values "Bank Account" and "Insurance".

For an eligible segment, 3 offers are assigned: 2 offers with an offer type of "Bank Account" and 1 with an offer type of "Insurance". The following getoffersForMultipleInteractionPoints() API call would produce incorrect results:

{DIP1,3,1,(2,Offertype=Bank account|string)

This call would return only 2 offers with an offer type of "Bank Account."

The following call would correctly return the wanted output:

{DIP1,3,1,(3,,(2,Offertype=Bank account|string)

Deployment successful even if interactive flowchart contains an unconfigured process


If you make some configuration change which places processes in interactive flowcharts into an unconfigured state, and you have deployed the interactive flowchart in the past, the interactive flowchart will deploy. Interactive flowcharts with unconfigured processes should not deploy.

Existing installer properties files are deleted after Marketing Platform installation in silent mode


If a previous installation in UI mode was performed, the and files are wiped out after you then perform Platform installation in silent mode.

WebConnector does not pick up default configuration when trying to save from GUI


WebConnector does not set the default values for fields when saving from the GUI.

Test Run shows results from first schema when 2 schemas are present

DEF054970, DEF055064

If more than one schema is present, test run results are from the schema that comes first alphabetically.

Validate flowchart fails when Mail List process is configured


"Validate Flowchart" fails to validate if a Flowchart Template created from a Batch Flowchart having MailList process is added into an interactive flowchart. "Validate Flowchart" displays "No errors detected in flowchart configuration". To avoid this problem, do not include batch flowchart templates in interactive flowcharts.

Removing a learning attribute from the model deletes the historical data for that attribute.


This occurs as part of the learning feature self-maintenance, to clear out unnecessary data. In the situation where you want to add back the attribute that was removed, the Learning system will learn again from scratch for that attribute (rather than rely on old history data). If you want to keep the history for an attribute rather than allowing the system to delete it, add it to the global setting, and then avoid using it by creating a learning model that does not use that attribute, and assign at the Interactive Channel level.

Offer parameterization does not support Date type fields.


When you are using the Offer Parameterization feature, if you use a table-driven offer, an incorrect date value is displayed in the offer attribute. To avoid this problem, do not use date fields in parameterized offers.

Cannot save an event pattern containing non-ASCII characters in its name.


If you save an event pattern with a name containing non-ASCII characters, the following error is displayed and the event pattern is not saved: "Name may only contain alphabetic, numeric or underscore (_) characters, and it must start with an alphabetic character." To work around this issue, save the event pattern again using a name that matches the conditions that are described in the message.

After the upgrade process to the current version of Interact, a message saying "Previous strategy deployments have been corrupted" is displayed during the validate mapping command.


After the upgrade is complete, editing a mapped profile table by clicking an existing interactive channel's Mapped profile table link and then clicking Edit mapping, clicking Validate Mapping displays the following error:

Validation failed. Previous strategy deployments have been corrupted. Please mark the strategies associated to this IC for deployment again and then try to deploy.

To work around this issue, mark the strategies associated with the interactive channel for deployment as described in the error message.

In Interact you cannot change the Campaign field name for the audience ID to a different value from the source field name.


In a batch flowchart, if a Select Process Box is used with an Interact list process box that creates a new table to export offer lists using white list (score override), the Campaign field name for the audience ID cannot be changed to a different value from the source field name. Interact uses the source field name in order to query the export table where the offer list would be, and if an alias is used for the audience ID in the Campaign field name, then Interact uses a query parameter that does not exist in the offer list. If this is not followed, a SQL error occurs during getOffers specifying that the source field name is an invalid identifier.