4.71¶
Cognigy.AI Handovers broken in versions v4.71 and v4.72
With Release v4.71.0, we have introduced an incorrect default behavior for how meta-data for Cognigy.AI Handovers are cached. This leads to flaky behavior in Handover sessions for Cognigy.AI in all versions of our v4.71 and v4.72 lineup. Immediately update to the newest patch versions or set the configuration below:
cognigyEnv:
LRU_CACHE_ENABLED: "false"
DNS Name Change Required
With the 4.71 release, DNS names for AI Copilot will change. If you have an on-premises installation, refer to the migration guide.
4.71.4¶
Cognigy.AI¶
Cognigy.AI Handover problem solved in v4.71.4
This version solves an issue with an incorrect caching behavior of Cognigy.AI Handovers by deactivating the cache by default. If you are upgrading to this version, the following configuration, which was necessary in the older version of v4.71 is NOT necessary:
cognigyEnv:
LRU_CACHE_ENABLED: "false"
Released April 5th, 2024
Bugfixes¶
- Deactivated the default meta-data caching option for Cognigy.AI Handovers (LRU_CACHE_ENABLED: false)
Cognigy Live Agent¶
Released April 4th, 2024
Bugfixes¶
- Fixed the issue where human agents were unable to log in to Live Agent under a high load when automatic assignment was enabled
4.71.3¶
Cognigy.AI¶
Cognigy.AI Handovers broken in versions v4.71 and v4.72
With Release v4.71.0, we have introduced an incorrect default behavior for how meta-data for Cognigy.AI Handovers are cached. This leads to flaky behavior in Handover sessions for Cognigy.AI in all versions of our v4.71 and v4.72 lineup. Immediately update to the newest patch versions or set the configuration below:
cognigyEnv:
LRU_CACHE_ENABLED: "false"
Released March 27th, 2024
Bugfixes¶
- Fixed the issue where messages were randomly missing during a handover to the RingCentral Engage provider
Infrastructure¶
Released March 13th, 2024
Cognigy Live Agent¶
- Fixed another issue where the
existingSecretKey
parameter within thecognigyOAuth
block would not be applied
4.71.2¶
Cognigy.AI¶
Cognigy.AI Handovers broken in versions v4.71 and v4.72
With Release v4.71.0, we have introduced an incorrect default behavior for how meta-data for Cognigy.AI Handovers are cached. This leads to flaky behavior in Handover sessions for Cognigy.AI in all versions of our v4.71 and v4.72 lineup. Immediately update to the newest patch versions or set the configuration below:
cognigyEnv:
LRU_CACHE_ENABLED: "false"
Released March 14th, 2024
Bugfixes¶
- Fixed the issue where handover requests were failing without displaying any errors in the logs
Infrastructure¶
Released March 13th, 2024
Cognigy Live Agent¶
- Fixed the issue where the
existingSecretKey
parameter within thecognigyOAuth
block would not be applied
4.71.1¶
Cognigy.AI¶
Cognigy.AI Handovers broken in versions v4.71 and v4.72
With Release v4.71.0, we have introduced an incorrect default behavior for how meta-data for Cognigy.AI Handovers are cached. This leads to flaky behavior in Handover sessions for Cognigy.AI in all versions of our v4.71 and v4.72 lineup. Immediately update to the newest patch versions or set the configuration below:
cognigyEnv:
LRU_CACHE_ENABLED: "false"
Released March 8th, 2024
Bugfixes¶
- Fixed the issue where Portuguese dates following the
Junho de 93
pattern were not recognized correctly - Fixed the issue where it is not possible to use a Custom URL for Azure LLM provider with domains other than
azure.com
- Fixed the issue where the Live Agent handover was failing
Cognigy Live Agent¶
Released March 8th, 2024
Bugfixes¶
- Fixed the issue where push notifications were not working
4.71.0¶
Cognigy.AI¶
Cognigy.AI Handovers broken in versions v4.71 and v4.72
With Release v4.71.0, we have introduced an incorrect default behavior for how meta-data for Cognigy.AI Handovers are cached. This leads to flaky behavior in Handover sessions for Cognigy.AI in all versions of our v4.71 and v4.72 lineup. Immediately update to the newest patch versions or set the configuration below:
cognigyEnv:
LRU_CACHE_ENABLED: "false"
Released March 5th, 2024
Improvements¶
- Improved the Package Upload capability to resume on connection failure
- Improved the default password policy for the organization to include a minimum of 1 special character and require a minimum length of 12 characters
- Added new voices for text-to-speech for the Deepgram provider
Bugfixes¶
- Fixed the issue where models are not marked outdated after changes to case-sensitive Intent mapping
- Fixed the issue where outdated NLU of non-primary locale is not reflected in the Flow list
- Fixed the issue where several copies of the same Knowledge Source were uploaded by clicking the Next button multiple times in the Knowledge AI wizard
- Fixed the endpoint name for AI Copilot
- Fixed the issue where entryId validation was missing when adding Keyphrases or Slots to Lexicon entries
- Fixed the issue of occasional failure in trained model invalidation
Cognigy Insights¶
Released March 5th, 2024
Improvements¶
- Moved the locale filters back to the additional filters panel
- Improved by hiding the grain label in the widget's detailed view
- Removed the redundant indent from the Transcript Explorer details
- Changed the UI of the filters panel
Bugfixes¶
- Fixed the issue where the header of the Transcript Explorer was overlapping table content when transcript details were open
- Fixed the issue where
service-analytics-conversation
was loggingValidation failed. Missing field 'organisationId'
- Fixed the issue where the first and last message timestamps in the Transcript Explorer details weren't adjusted to the current time zone
Cognigy Live Agent¶
Released March 5th, 2024
Bugfixes¶
- Fixed the issue where the line break was not correctly encoded in the Reply to bot section
- Fixed the issue preventing Live Agent upgrade with a non-root database user
Cognigy Voice Gateway¶
Released March 5th, 2024
Features¶
- Implemented streaming capability with the Elevenlabs Speech provider
Bugfixes¶
- Fixed the issue where an error occurred during a
say
task with pre-cached audio using Deepgram - Fixed the issue where the Transcribe feature was not working
Infrastructure¶
Cognigy.AI + Insights¶
If you are not using cognigyLiveAgent.existingSecret
in your values
local file, then you need to add the helm.sh/resource-policy: keep
annotation to the cognigy-live-agent-credentials
secret.
You can do this by using the following command. Replace <namespace>
with the namespace where Cognigy.AI is deployed.
kubectl annotate -n=<namespace> secret cognigy-live-agent-credentials helm.sh/resource-policy=keep
Cognigy Voice Gateway¶
- Change the default value of
.Values.api.enablePrepareCognigyData
totrue
. - This change will modify the startup behavior of the API server.
- The
admin
user will now have a randomly generated password instead ofadmin
. - A user named 'cognigy-ai' is being created for Interaction Panel calls.
- If not already present by that name, a new Service Provider named
IP Test Call Manager
will be created. Rename your existing service provider, used for the Interaction Panel, toIP Test Call Manager
. - An API token is created and connected to the new service provider.
- Add Ingress for
Homer
- Add Middleware
ipwhitelisthomer
- Add Middleware
homerauth
- Update
redis
to7.2.4-debian-11-r3
- Update
redis high availabilty
images:redis
image to7.2.4-debian-11-r3
redis-sentinel
to7.2.4-debian-11-r4
redis-exporter
to1.56.0-debian-11-r1
- Update
feature-server
Deployment and StatefulSet change theOTEL
environment variable from"1"
to"true"
- Update the
feature-server
Deployment and StatefulSet templates for TTS streaming fromvalue: {{ if .Values.featureServer.enableTtsElevenlabsStreaming }}{{ print 0 | quote }}{{ else }}{{ print 1 | quote }}{{ end }}
to{{ not .Values.webapp.enableTtsElevenlabsStreaming | quote }}
- Update the
api-server
Deployment TTS streaming template fromvalue: {{ if .Values.featureServer.enableTtsElevenlabsStreaming }}{{ print 0 | quote }}{{ else }}{{ print 1 | quote }}{{ end }}
to{{ not .Values.webapp.enableTtsElevenlabsStreaming | quote }}
Version Compatibility Matrix¶
The version compatibility matrix was updated for the following Cognigy products: