---
title: "Release 6.3.2"
description: "A \"client left the chat\" entry in the dialog feed when a chat is ended in the widget, a readable chat-close reason, correct skill group counters in the side menu, and more stable queue storage."
---

# Release 6.3.2

Release 6.3.2 adds a dialog feed entry when a client ends a chat in the widget and translates the chat-close reason. It also fixes skill group counters in the Operator Panel side menu and stops processed service events from piling up in the instance's queue storage.

## Operator Panel

**New**

- **"Client left the chat" entry for the widget.** When a client ends a chat with the "End chat" button in the website widget, the dialog feed now shows an entry "Client name left the chat", as it already does for messengers. Previously the operator saw only the closing message with no explanation and could assume they had closed the dialog themselves. Closing of the chat and ticket, statistics and CSAT are unchanged.

**Changed**

- **The chat-close reason is readable.** In the chat-close line of the dialog feed, the mixed-language text with a technical code is replaced by a full translation: "Client name left the chat. Chat closed (via widget)", "… (by timeout)", "… (by the exit button)" and so on. Translations are available for all interface languages. An unknown reason is shown as before.

**Fixed**

- **Skill group counters in the side menu.** On instances with fast search and counting of cases, every skill group showed 0 next to its name even though the group's list was not empty. The counter now matches the number of chats in the group's list. If a subject belongs to several skill groups, its chats are counted in each of them.

## Stability

**Fixed**

- **Processed service events no longer pile up.** Completed jobs of internal queues (ticket events, statistics, scenario projections, custom module analytics, FastLine data transfer) used to stay in the instance storage, which grew with every event until the server ran out of memory. Processed jobs are now removed immediately. Side effect: every scenario save again queues a refresh of its projection, and repeated analytics with the same key runs. This release does not delete jobs that have already accumulated: for large instances the ConnectiveOne team clears them at an agreed time.