> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cognigy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 4.32

<Warning>
  With release 4.30.0, we have officially marked our Kubernetes repository as `deprecated`. If you are an `on-premises` customer and you are running Cognigy.AI/Cognigy Insights yourself, have a look at our [Helm Chart](https://github.com/cognigy/cognigy-ai-helm-chart), which we have crafted for Cognigy.AI/Cognigy Insights! Our Kubernetes repository will still receive updates `until 31st December 2022`.
</Warning>

## 4.32.1

### Cognigy.AI

**Released** August 24, 2022

#### Bug Fixes

* Fixed a bug where merging a package was deleting NLU models

## 4.32.0

### Cognigy.AI

**Released** August 17, 2022

#### Improvements

* Remove "powered by Cognigy" link from webchat when whitelabeling flag is enabled
* Add default, webchat, plugin Adaptive cards rendering to Interactive Panel
* Improved by adjusting the agent assist flow node
* Improved by making the conversation counter timezone aware
* Improved the error message when executing a Flow Node failed

#### Bug Fixes

* Fixed a bug where the Salesforce Handover Integration doesn't provide the full conversation history
* Adjusted log levels from 'error' to 'debug' for anonymous callers
* Fixed a bug where two identical user IDs would create different Contact Profiles when containing a "+" sign
* Fixed a bug where the agent assist output appeared in channels other than live-agent
* Fixed a bug where Initializing a second handover request in live agent using a different inbox would fail
* Fixed a bug where packages with intents created with a name starting/ending with white space were not accepted
* Fixed a bug where the password reset functionality would not work for users which are part of multiple organizations
* Fixed a bug where AI channel preview for Adaptive Card output type was not working

### Cognigy Insights

**Released** August 17, 2022

#### Improvements

* Improved by adding the info Tooltips in Insights dashboards
* Improved by including 'today' under 'Last X days'
* Improved by Making Contact ID copyable in the Transcript explorer
* Changed duration formatting for the number charts
* Changed background color in transcript explorer
* Fixed sidebar animation
* Added Search field for Flows + order of flows for the Transcript Explorer

#### Bug Fixes

* Fixed a bug: Message explorer search filter doesn't work
* Fixed a bug: The user has to refresh their Insights dashboard to see the Actual Active contacts
* Fixed a bug: Close dropdown icon in the Insights dashboards left sidebar doesn't work
* Fixed a bug: Close dropdown icon in the Insights dashboards left sidebar doesn't work

### Cognigy Live Agent

**Released** August 17, 2022

#### Improvements

* Improved by adding the new status "Aborted" to conversations that didn't get a customer response. It is configurable under the Account Settings section
* Improved by adding a link to inbox settings in the assist bot sidebar and persisting selected flow in conversation when the sidebar is closed

#### Bug Fixes

* Fixed a bug where the text of user messages in assist bot was not correctly aligned
* Fixed a bug where the input box was not staying at the bottom on big screens, and assist bot chat messages were misaligned

### Infrastructure (AI + IN)

#### Stateful services

To improve the functionality and fix known security vulnerabilities in the dependencies Cognigy.AI/Cognigy Insights uses, we have updated the following dependencies:

* Redis, from `v5.0.8` to `v5.0.14`
* RabbitMQ, from `v3.8.3` to `v3.9.20`

In addition, we have released a new version of our `MongoDB Helm Chart` which you can use to deploy a 3-node MongoDB replica-set. We have increased the MongoDB version from `v4.2.5` to `v4.2.21` in this new Helm Chart. For more info, [see](https://github.com/Cognigy/cognigy-mongodb-helm-chart).

Updating to this release requires you to update these `stateful services`. Doing this will require restating all application Pods and will come with a couple of seconds of downtime. In order to restart all Pods after you have updated MongoDB, RabbitMQ, Redis and Redis-persistent, you can use the following command:

```bash theme={null}
for i in $(kubectl get deployment --namespace <target_namespace> --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}'|grep service-)
do
kubectl --namespace <target_namespace> rollout restart deployment $i
done
```

Be sure to replace the `<target_namespace>` with e.g. something like `cognigy-ai`.

#### NLU services - optional

In order to avoid that you need to provision unnecessary resources in your Kubernetes clusters, we now require you to select which `NLU languages` you actually need in your Cognigy.AI setup. If you, for instance, want to only build bots in English language, you can activate English NLU by doing the following in your `values.yaml` file:

```yaml theme={null}
## Enable your choice of NLU service by following the below example
serviceNlpScoreEn:
  enabled: true
serviceNlpTrainEn:
  enabled: true
```

#### New services

You will also see that this release introduces two new microservices:

* service-insights-ui
* service-insights-api

We are slowly separating Cognigy.Insights from Cognigy.AI in order to improve scalability, stability and performance of both products. To prepare your installation, follow these steps closely in order to make sure that the upgrade is smooth:

Create a new DNS entry for `service-insights-api` and point it towards your loadbalancer which was provisioned when you have installed Cognigy.AI. A potential example would be the following:

Let's assume that your `Cognigy.AI API` is available on the DNS name `api-trial.cognigy.ai` a good name for the new Insights API service would be `insights-api-trial.cognigy.ai` - so we e.g. just prefix the Cognigy.AI API address with `insights-`.

Using a command like `dig` on Linux should reveal that both DNS names point to the same Loadbalancer address:

```bash theme={null}
dig api-trial.cognigy.ai

; <<>> DiG 9.10.6 <<>> trial.cognigy.ai
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26015
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;trial.cognigy.ai.              IN      A

;; ANSWER SECTION:
trial.cognigy.ai.       300     IN      CNAME   ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com.
ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com. 60 IN A 52.29.55.202
ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com. 60 IN A 3.121.18.227
ae79c0ec73eca4d64a0509f7a75fe42a-1344350581.eu-central-1.elb.amazonaws.com. 60 IN A 3.64.138.183

;; Query time: 30 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed Aug 10 18:37:42 CEST 2022
;; MSG SIZE  rcvd: 181
```

Performing the same `dig` command for the new Insights API server should return similar data.

The last step is to make sure that you add the following key/value pair to the `cognigyEnv` section of your `values.yaml` file:

```yaml theme={null}
FEATURE_USE_SERVICE_INSIGHTS_UI: "true"
```