> ## 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.40

<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.40.3

### Cognigy.AI

**Released** December 5, 2022

#### Bug Fixes

* Reverted NodeJS upgrade for three additional microservices sending outbound HTTP calls as the newer NodeJS version can break compatibility with certain APIs

## 4.40.2

### Cognigy.AI

**Released** November 30, 2022

#### Bug Fixes

* Reverted NodeJS upgrade for two microservices sending outbound HTTP calls as the newer NodeJS version could break compatibility with old APIs which still use old TLS versions (e.g. TLS v1.0)
* Fixed a problem related to Voice Activity Detection always being active

## 4.40.1

### Cognigy.AI

**Released** November 29, 2022

#### Bug Fixes

* Fixed a bug where internal state could be reset in certain situations which leads to e.g. the Context being reset in the middle of conversations

## 4.40.0

### Cognigy.AI

**Released** November 29, 2022

#### Improvements

* Improved the UX of the Voice Preview Dialog
* Improved by updating the Webchat Widget to latest version (v2.44.0)
* Improved by allowing to navigate Positive/Negative confirmation words using Enter key
* Improved by adjusting the generic Voice Flow Nodes "Barge In" and "Play"

#### Bug Fixes

* Fixed a bug where when using a Think node in a flow with Complete Goal nodes defined, these goals were not available in the OData Sessions endpoint.
* Fixed a bug where an Execute Cognigy NLU node would not trigger an intent's default reply. A new option Process Intent Default Reply has been added to the Execute Cognigy NLU node. This option is disabled by default, which means the default reply is not processed. However, when it is enabled, the default reply is processed in the same manner as when triggered by means other than the Execute Cognigy NLU node.
* Fixed a bug where execution count for realtime translation with DeepL did not work properly for English and Portuguese.
* Fixed a bug where English money slots would sometimes be recognized as date slots.
* Fixed a bug where service-parser would crash when importing Keyphrases with an empty data object.
* Fixed a bug where CognigyScript in lookup Nodes would log errors.
* Fixed a bug where the media file attached from WhatsApp endpoint is not visible in the interaction panel during a live-follow
* Fixed a bug where voice name and language gets reset after audio provider is changed

### Cognigy Insights

**Released** November 29, 2022

#### Improvements

* Changed Step Explorer visualization in order to support larger amounts of data during visualization phase

#### Bug Fixes

* Fixed a bug where live agent escalations records would not get inserted because of corresponding session information
* Fixed a bug where Transcript Explorer would show an incorrect number of sessions whenever the channel name differs for the same sessionID
* Fixed a bug where the conversations line chart in detailed view was crashing on the "Today" time filter

### Cognigy Live Agent

**Released** November 29, 2022

#### Improvements

* Improved by adding a raw data modal for the whisper assist and assist bot forwardable messages - allowing our customers to inspect the data they will forward for all channels Cognigy.AI supports

#### Bug Fixes

* Fixed a bug where the email transcript was missing descriptions for audio, video, image and list messages
* Fixed a bug where the translations in the success message for updating agents inside an inbox was not displayed correctly
* Fixed a bug where navigating to a nonexistent inbox in inbox settings will let you edit it, even if it does not exist. Resulting in an error when updating

### Webchat Widget

You can find the release notes for our Webchat Widget on [GitHub](https://github.com/Cognigy/WebchatWidget/releases) as usual. The latest release of our Webchat Widget at the time of releasing all other Cognigy products is [v2.44.0](https://github.com/Cognigy/WebchatWidget/releases/tag/v2.44.0).

### Infrastructure (AI + IN)

#### Stateful services

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

* RabbitMQ, from `v3.9.20` to `v3.9.24`

**Important: Once you have upgraded to the new release containing the new RabbitMQ version, run the following command to rollout (restart) all Pods that run in your cluster - be sure to replace the `<target_namespace>` accordingly:**

```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
```

#### New service

This release also adds a new service called `service-collector`. This microservice will be used in the neare future to collect analytics information for Cognigy Insights so we can also ingest data from other Cognigy products such as Cognigy Live Agent and Cognigy Voice Gateway.

**Important: In case you have overwritten the replica-count (or other aspects) for specific services in your own `values` file, make sure that you also apply the same configuration for the new `serviceCollector` section in your `values`.**

#### Config change

In case you are already using the `call capabilities within the Cognigy.AI Interaction Panel`, you have to make sure that you change the following ENV variable in the `cognigyEnv` configmap section:

```text theme={null}
VOICE_GATEWAY_PREPARE_CALL_API
```

from value: `/api/v1/call/prepare` to value: `/api/v2/call/prepare`.

In addition, you have to set the following ENV variable so `Cognigy Live Agent` will be able to display attachments that have been uploaded through Cognigy.AI endpoints:

```text theme={null}
RUNTIME_FILE_MANAGER_CORS_WHITELIST
```

the value should be at least set to the `frontend DNS name` of the `Cognigy Live Agent` installation - an example value would be: `https://dev-live-agent.cognigy.ai`