Known issues

The following table lists the known issues in Unica Journey 12.1.6:

Defect ID Known Issue
HMA-355198 cluster - 1216 - engagement split not processing data after getting responses also
HMA-349054 DB2-specific database file is not available within the /ddl/discover_sql_files/ folder.
HMA-348450 Loop - audience accepted time is showing always same in all iteration on loop stats
HMA-355188 1216_Cluster -Import Journey export Journey is not working
HMA-348752 (Imported Journey)Engagement Split should be greyed out when configured ES-Whatsapp touchpoint is deleted
HMA-349354 Event change for Engagement Split configuration done for paused Journey state should be allowed as this change is done before Publish state
HMA-349383 Audience accepted time is showing always same in all iteration on loop stats
HMA-349494 EngineScript.sh start command does not start the engine
HMA-352777 Engagement Split warning message always displays wait time of 30 mins irrespective of time set for 'Engagement_Split_Waittime' variable.
HMA-354338 NPN - Performance is very slow, Journeys listing loads in more than a min when launched.
HMA-354578 SalesForce Goals - Goals set for Salesforce counting failuer count also
HMA-354760 NBO- View mode of Email touchpoint partially displays mapped Interactive channel fields
HMA-354762 Inconsistent (facebook) - Some times after copying journey with Facebook TP , Faceboolk TP configurations gets lost
HMA-354809 REGBB - EngagementSplit configuration persists and journey gets published too when mapped WhatsApp touchpoint is deleted for Copied and Imported Journey
HMA-350649 ComplexBuilder-Numeric- On Decision split with Numeric type function #SUM($CustomerID ,10,20 ) is not null - not working
HMA-338279 SMS delivered from Journey do not send latest URL configured in SMS template in deliver
HMA-355004 If user selects only engine, templates and kafka its showing error in journey installation log
HMA-355002 Listing pages for journey on New UI not displayed with ISAM login method
HMA-354994 SQL exceptions in engine logs for REST TP when jouney field is not mapped with API response field
HMA-348238 Updating Data Definition for existing Journey is giving 500 internal server error(12.1.3/12.1.5)
HMA-355068 Cluster -1216- If user stops the services of any secondery node - primary and other secondary node stops processing records and gets hanged