Known Issues
The following table lists the known issues in this release:
Known Issues in 26.1.0.IF02
| Issue ID | Description |
|---|---|
| HMA-420710 | When you upgrade an existing Unica Detect installation with
the Interim Fix installer in console mode, it does not populate
the existing settings: domain name, host name, port, and database
connection details. You must reenter them manually. The Platform
installer does populate these settings. This happens because the
Detect installer creates only the
installer_ud_write<version>.properties
files, not the
installer_ud<version>.properties file it
uses to read the existing values. |
| HMA-420660 | On a fresh deployment, the Unica Detect installer does not
create the ud_profile_storeback table in the
Detect datasource schema (UnicaDetectDS)
because a DDL script fails during installation. The other
ud_* tables are created, but
ud_profile_storeback is missing. |
| HMA-420608 | The Master Profile creation dialog incorrectly states that you can edit a Master Profile. |
| HMA-420586 | In the Detect Engine, processing Milestone transactions for Action-based Event pipelines can reset the schedule for Time-based Reminders or delay them. |
| HMA-420386 | You cannot edit enrichments created in earlier versions because the stricter schema validation in IF02 is not backward compatible. |
| HMA-419967 | In Pipeline Reports, when a pipeline has more than one destination, the "Events Sent by Event ID" section does not report success or failure for each destination. |
| HMA-419910 | Columns appear in the wrong order on the Aggregates & Enrichments list page. |
| HMA-419903 | On the pipeline canvas, clicking Collapse All leaves broken, partially visible condition blocks on screen. |
| HMA-419379 | In Pipeline Validation, if you set the Action Target Value or Target Time below the existing Reminder or Milestone thresholds, no error appears immediately. The error appears only when you submit the pipeline for approval. |
| HMA-419376 | The Time Reminder validation error message says "target deadline" instead of Target Completion Time. |
| HMA-419200 | Some Progressive Attribute names in the UI don't match the
keys in the downstream JSON message. Target Value is sent
as totalValue, and Target Completion
Time is sent as targetDeadline. |
| HMA-418892 | In Action-based Event pipelines, Time Reminders trigger several minutes later than scheduled, and the delay increases with each reminder. |
| HMA-418870 | On the pipeline canvas, the Action node card shows only the Action name. It does not summarize the fulfillment criteria (target value and duration). |
| HMA-418357 | The Detect installer completes with
NonfatalInstallExceptions and reports errors
about missing configuration files. |
| HMA-420969 | Saving an enrichment with a new Storeback attribute does not
add that attribute to the profile_storeback
table. The table row is created only after a transaction is
processed. If you create a Lookup Attribute that references the
new Storeback attribute before processing any transactions, the
retained Derived Attribute and Lookup Attribute both appear
blank in the
pipeline destination output. |
| HMA-420955 | A Derived Attribute can have both Retain and Storeback enabled while a retained Lookup Attribute also references it. In that case, the Derived Attribute appears blank (null or empty) in the pipeline destination payload. The Lookup Attribute still shows the correct value, and the derived value is still saved to the Storeback table. |
| HMA-420952 | On the Aggregates & Enrichments page, you can turn off Storeback on a Derived Attribute and save the enrichment even when a Lookup Attribute still references it. No dependency validation error appears. This can leave the Lookup Attribute configuration orphaned and cause data resolution or pipeline errors at runtime. |
Known Issues in 26.1.0.IF1
| Issue ID | Description |
|---|---|
| HMA-416968 | Newly deployed pipelines fail to trigger transactions until a manual Detect Engine restart is performed following SiteMinder SSO integration and Tomcat restarts. |
| HMA-416809 | In Feed Mapping, adding an attribute beyond the 10-row page limit navigates the row to Page 2 without shifting the user's view focus to the newly added row. |
| HMA-416805 | Feed Engine ignores the explicitly assigned Key Attribute in
Feed Mapping and defaults key resolution to the Primary Key
(AUDIENCE_KEY) during runtime
processing. |
| HMA-416695 | NullPointerException in ObjectParserHelper
when parsing formatted date strings (e.g., yyyy-MM-dd
HH:mm:ss) — the parser falls back to
parseLongSafe, fails, and crashes batch
processing. |
| HMA-416694 | FeedParserFlow throws PathNotFoundException
when evaluating JSON paths against stringified (escaped) JSON
fields received from CDP. The parser does not auto-deserialize
escaped JSON strings. |
| HMA-416457 | Installer generates detect.xml with missing
driverClassName and url
for UnicaPlatformDS, and leaves the
UnicaDetectDS password in plain text
(un-encrypted).Workaround: you can manually update the
detect.xml. |
| HMA-416399 | Detect Engine processes transactions with arbitrary past or future timestamps without validating them against server clock thresholds or a sliding time-window tolerance. |
| HMA-416398 | Multi-feed triggers leak empty tuple attributes across different feed event streams in destination payloads. Attributes from unrelated feeds are sent with blank/null values. |
| HMA-416305 | Upgrade logs aren't generated in
<DetectHome>/tools/upgrade path during
26.1.0 to 26.1.0.IF01 update, preventing audit trail of
migration actions. |
| HMA-416181 | NullPointerException in TriggerEvaluatorFlow
during batch evaluation when processing transactions with
updated DateTime source formats. Key retrieval fails on null
variant value. |
| HMA-416178 | Date/Time parsing fails due to case-sensitivity mismatch
between UI sourceDataFormat and backend
DateTimeFormatter.Workaround: restart
the Detect Engine to reload configuration. |
| HMA-415637 | Live Conditions UI fails to display the Estimated Count when a Live Condition is used as audience criteria or configured within the condition set. |
| HMA-415409 | On the Dashboard page, the "Total Recharges" feed label is getting cropped/truncated. |
| HMA-414774 | On the Live Segment UI, users can't distinguish between Edit and View mode. New segments open in a mode requiring an extra edit action instead of being directly editable. |
| HMA-406299 | You cannot update or modify the scheduled time in the Active Days and Times of Week section of a pipeline configuration. |
| HMA-412332 | Datetime and Timestamp profile attributes display as plain text input boxes instead of calendar or time pickers in the user interface. |
| HMA-417297 | When constructing an expression for a derived/transformed attribute using profile attributes with list data types or list array syntax (e.g., [profile.city, profile.country]), attempting to save the enrichment throws a parsing error: "The value '[...]' of the '<attribute_name>' derived attribute has parsing errors." |
| HMA-417296 | When a tuple attribute with a list data type (e.g., List(String)) is created via a Lookup enrichment and retained for downstream use, referencing this attribute within a transformed or derived attribute expression causes a validation failure upon saving: "the expression is expected to be of the 'List(String)' type, but was of the 'unknown' type" |
| HMA-417247 | In the Contact Policy section of the Pipeline editor canvas, the info tooltip for Total Triggers Limit and Per User Limit displays incorrect terminology — uses "pipelines" instead of "events" in the message. |
| HMA-417214 | When a tuple attribute is created in Feed Mapping using a list data type (e.g., List(String), List(Int)), the Pipeline Trigger Condition builder fails to populate any conditional operator options in the operator dropdown, blocking pipeline configuration for list-based attributes. |
| HMA-417136 | Pipeline fails to deploy with "Failed to generate backend expression" error when feed attributes are not mapped to a Profile. Publishing a feed without binding a Profile or primary key attribute succeeds, but deploying a pipeline using that feed throws a backend expression generation error. |
| HMA-417399 | NullPointerException occurs during transaction processing when pipelines use secondary (non-Master) profile attributes mapped in feeds. The Detect Engine crashes during state/attribute evaluation when processing transactions matching feeds with both Master and secondary profile attributes. |
| HMA-417425 | "Send for Approval" fails with "Invalid profile attribute" error when non-Master Profile attributes are selected as destination attributes in the pipeline Destination Configuration. The UI validation logic strictly limits valid destination attributes to the Master Profile schema. |
| HMA-417428 | Intermittent tuple attribute dropdown pollution across trigger conditions when duplicating pipelines or switching feed applications. Some condition rows display tuple attributes from a different feed application instead of the currently active one. |
| HMA-417432 | Intermittent 2–3 second delay when opening dropdown menus on initial interaction or after inactivity across the Detect UI (Feed Application selection, Profile attributes, Data Types, Trigger Condition operators). |
| HMA-417434 | When the Unica Detect UI session expires, the UI floods the screen with stacked raw JSON error toasts ({"status":500, "error":"Internal Server Error"}) instead of displaying a single clean "Session Expired" prompt and redirecting to the login page. |
Known Issues in 26.1.0
The following table lists the known issues in this release 26.1.0:
| Issue ID | Description |
|---|---|
| HMA-406192 | An "Unsupported Tuple Attribute" error occurs when you use profile attributes in a trigger configuration. |
| HMA-412300 | Client ID and Secret generated by the installer cause a 401
Authentication Required error for the CLI tool and the
Engine.Workaround: Manually generate credentials by
running clientDetails.sh -a UnicaDetect, and then
update the app.conf file for the CLI tool and the
Engine with the correct client ID and secret. |
| HMA-410653 | On Dashboard charts, the Total Events Sent and Overall Trends data labels are cropped at the top boundary of the chart container when values reach the Y-axis maximum. |
| HMA-409273 | When you duplicate a pipeline, the new pipeline is created with a blank configuration, and all settings from the source pipeline are lost. |
| HMA-412253 | You can't edit or update a Master Profile after initial creation. The system locks the profile, and the user interface doesn't provide an option to modify attributes or mappings.Workaround: Manually delete the feed parser mappings and profile tables directly from the database, and then re-add the profile with a new ID.Note:Direct database access is required. Proceed with caution. |
| HMA-406299 | You cannot update or modify the scheduled time in the Active Days and Times of Week section of a pipeline configuration. |
| HMA-409200 | Changing the enrichment timing from preAggregation to postAggregation fails without displaying an error message, even though the user interface displays a false-positive success message stating "Enrichment added successfully." |
| HMA-412332 | Datetime and Timestamp profile attributes display as plain text input boxes instead of calendar or time pickers in the user interface. |
| HMA-412329 | In the pipeline configuration canvas, mindmap connector lines misalign while you configure nested condition blocks. |
| HMA-412330 | On the Enrichment Configuration page, the text on the Cancel button is truncated and displays as "Canc...". |
| HMA-412772 | Inability to disable Feeds via CLI/Swagger forces manual database updates to edit mappings |
| HMA-412907 | The pipelines fail to trigger when a list(bool)
transformed attribute is created as a retained enrichment attribute
along with lookup and derived attributes. The engine crashes with a
Duplicate key exception during schema merging,
causing the Kafka stream to fail. The enrichment also becomes
uneditable in the UI. |
| HMA-412984 | When attempting to save an enrichment configuration that uses a
function-based derived attribute with
get_last_five_activities, the save operation
fails. |
| HMA-413420 | When the Detect user interface remains idle for an extended
period, subsequent actions may result in a 422 Unprocessable
Entity error.Workaround: The application typically recovers and reconnects to the database automatically within 4 to 5 minutes. If you encounter this error, wait a few minutes for the connection to refresh, or refresh your browser to re-establish the session. |