Known issues
The following table lists the known issues in Unica Journey 12.1.11:
| Defect ID | Known Issue |
|---|---|
| HMA-402962 | REGBB - This specific Journey is not getting exported |
| HMA-363512 | Db2_docker-(inconsistent) Some times audiences available in loop is getting stuck and not moving ahead. |
| HMA-403232 | Upgrade 12.1.9 to 12.1.11 - Journey audiences available in delay TP in paused journey are not getting processed by Publish TP available next to Delay TP. |
| HMA-402783 | While upgrading Journey from version 12.1.7 to 12.1.11, one non-fatal error received. |
| HMA-402860 | Journey having Rest TP with responses not getting deleted. |
| HMA-402809 | Mobile Push some times while saving mobile push TP along with Eng split its not saving journey and showing message "some thing went wrong on server" |
| HMA-402821 | Some time data gets rejected saying required field is not available - where that required field is not a part of that Journey DD. |
| HMA-402201 | Journey with CIF external ES exported journey if gets import then external source configuration in ES is getting lost |
| HMA-363277 | DB2 Link Salesforce & twilio goals count is not updating on goals page. |
| HMA-402608 | After upgrading from Oracle 12.1.8 to 12.1.11, the Journey Engine
fails to process Deliver channel responses, resulting in the error
Work Around: Upon investigation, it was identified that there was null constraint on the email column of JourneyDeliverResponseMaster table which was removed in 12.1.0.3 script. However, the sql statement in 12.1.0.3 might not have taken effect. In that case, please run below query on journey database/schema to address this issue. ALTER TABLE JOURNEYDELIVERRESPONSEMASTER MODIFY EMAIL NULL; This issue is not applicable for clean install of 12.1.11 or upgrades from 12.1.0.3 to 12.1.11 |
| HMA-400964 | Import Journey is not working if have REST TP
configured. Description: When importing a journey canvas containing REST touchpoints from a JRE 1.8 environment to a JRE 17 environment, the import fails if any REST touchpoint is configured with custom headers or request parameters. This issue is expected to be rare, as export/import operations are typically performed between identical environments (for example, from a 12.1.11 staging environment to a 12.1.11 production environment). |
| HMA-401083 | Docker MSSQL - Audience Archival is not working
(non-jdk17). Workaround: Drop the A_<source_table> table if its column order does not match the column order of the corresponding <source_table>. Recreate the table using a CREATE TABLE SQL command that follows the column order defined in the source table. Example: If column order of A_JourneyAudienceFlow does not match with that of JourneyAudienceFlow, then run below commands: DroptableA_JourneyAudienceFlow CREATETABLEA_JourneyAudienceFlow( idBIGINTNOTNULL, audienceIdBIGINTNOTNULL, nodeIdBIGINTNOTNULL, edgeBIGINTNOTNULL, audienceStageBIGINT, directionBITDEFAULT0NOTNULL, logTimeStampDATETIME2, createdDateDATETIME2, versionBIGINT, isProcessedBITDEFAULT0NOTNULL, logTimeStampEpochBIGINT, createdDateEpochBIGINT, iterationBIGINTDEFAULT1NOTNULL ); Provided that JourneyAudienceFlow has exactly same order of columns in its definitionYou can use any database viewing software to view the column order of any particular table. |
| HMA-381896 | REGBB_ Ms sql server - Rest TP - if Completed journey having rest TP with responses - journey is not getting delete. |
| HMA-382025 | CC - REGBB - If CC is down and Pratition wise CC flag is enabled then though journey is not configured with CC all the audiences goes in waiting state. |
| HMA-381473 | Salesgoals - Goals data is not getting available gols page instantly and if user adds non frequency based goals then not showing old responses on goals page. |
| HMA-379675 | Extra validation 'Data not found' is received on deleting Journey. |
| HMA-376121 | When we removed the license parameter from the jvm its gives Error for adding Link connection. |
| HMA-375720 |
Oracle upgraded setup - Not able to configure SMS whatsapp and push deliver touchpoints. Need to drop constraint SYS_C0037600 on DeliverMetaData table |
| HMA-375744 | ISAM- On ISAM setup opt in opt out not working in Journey |
| HMA-375523 | Opt out - Whatsapp TP- Postgres - Audience which is not in opted out state - also getting added in opted out state of TP |
| HMA-369764 | Multiple engine nodes - Performance issues observed during longevity runs |
| HMA-368281 | Milestone processing service needs enhancement when large audience set matches with the applied condition of milestone |
| HMA-375637 | Two ES - If journey is having two ES with data refresh enabled, then when refresh data comes stats counts mismatches |
| HMA-376226 | Clicking on view of journey in journey approval gives 404 error on setup configured with ISAM login method. |
| HMA-375085 | Retry - On retry page - with larger data - Retry job gets completed within time but data is not getting available quickly on Retry page and not having auto refresh to show case data on retry page |
| HMA-374895 | Retry - 12.1.7 to 12.1.9 DB2 - for SMS for some audiences retry not working and showing message data not found. |
| HMA-374380 |
SSL_Kafka - If Journey hosted on Machine A and SSL_kafka on other machine then its showing NullPointerException: null value in entry: ssl. |
| HMA-373789 | In Journey Overview report, appearance is not as expected. |
| HMA-373648 | Optin-out - In CC if audience id value is empty and in Journey payload also having empty value for same audience field opt out is not working. |
| HMA-373306 | After deleting Decision split its UI gets distorted |
| HMA-372432 | org.springframework.dao.DeadlockLoserDataAccessException error observed for delete & move operations |
| HMA-372430 | archival.AudienceMove processing needs performance improvement |
| HMA-372301 | Observing DataIntegrityViolationException for AudienceOptInOutCheckUtility.saveAudienceResponse while processing large data |
| HMA-372299 | Opt out processing needs improvement. |
| HMA-372006 | Time taken for consent data insertion to journey tables needs improvement |
| HMA-371436 |
Status of all audiences is not getting updated to JOURNEY_COMPLETED for journey with re-enter contacts selected |
| HMA-371356 | Journey processing gets degraded if re-enter contacts is chosen for a journey |
| HMA-369487 | Irrespective of Dedupe settings applied on a field duplicate data is
observed in Journey when data is sent through Campaign. Since there are duplicate data in same batch and the data is processing in multiple threads, at the time of process checks if the record already exist into the system it gets false. Further, till the time it inserts into the system (db tables) the same entry would be done by another process. Hence, results are duplicate data insertion. |
| HMA-375046 | Status of all audiences is not getting updated to JOURNEY_COMPLETED for journey with re-enter contacts selected. |
| HMA-373961 | SSL_SASL - Kafka topic is not getting created on SSL_SASL kafka where internal kafka is standalone kafka. |
| HMA-370171 | If you configure a Journey with Deliver Push or copy an existing Journey with Push configuration, publish and pause the Journey, you cannot edit the application selected for Push Touchpoint. |
| HMA-362126 | Postgres - Error observed when trying to create Duplicate copy for Imported Journey. |