---
title: "Release 5.17.2"
description: "All changes of release 5.17.1 plus fixes: JSON editor suggestions in Scenario Builder are fully readable, the internal note and operator message in chat no longer glare, chat closing is no longer duplicated, a Fast Line Pro knowledge base segment can be added on Dify v2, and \"Average chat reaction time\" shows \"—\" instead of a false zero."
---

# Release 5.17.2

A patch release. It contains **all changes of release 5.17.1** — see the [release 5.17.1 notes](/en/releases/5.17.1.md) — and adds five fixes: JSON editor suggestions in Scenario Builder, internal note colors in chat, double chat closing, adding a segment to a Fast Line Pro knowledge base, and how the average reaction time is shown in statistics. The "Average chat reaction time" column in the statistics table now looks different — see "Please note".

## Scenario Builder

**Fixed**

- **Suggestions in the JSON editor of action parameters are fully readable.** When you typed in the JSON mode of an action node's parameters (right panel), the suggestion list appeared, but its left part was cut off by the panel's frame, so the text could not be read. The list is now fully visible: it may extend beyond the panel over the canvas. The same applies to the JSON data in the scenario run window.

## Operator panel

**Improved**

- **The internal note and the operator's message no longer glare.** In the Lara, Material, and Nora themes, an internal note in chat was a solid bright orange card with white text that was hard to read. In the Nora theme, the operator's own message looked the same way. Now, in all five themes, the note has a pale orange background and dark text, and the operator's bubble in Aura, Material, Lara, and Nora has a pale background and dark text, as in the Aura theme. The same applies to "from another conversation" cards. In the Brutal theme the operator's bubble stays saturated — this is intended in that theme.

**Fixed**

- **Closing a chat is no longer duplicated.** When an operator's tab sent "Close chat" with a status twice almost simultaneously, the chat was closed twice: the timeline showed two close entries, and statistics and the close event for the bot were counted twice. Now only the first request closes the chat, and the second one duplicates nothing.
  - Side change: a repeated "leave chat" by an operator in a chat where another operator remains, or in a group chat (for example, a Telegram group), no longer closes that chat.

## Statistics

**Fixed**

- **"Average chat reaction time" shows "—" when there is no data.** In the "Dialogs" table on the "Dialogs" tab, this column showed 0 in almost every row. In fact, the average does not include the operator's first reply (that is shown by "First reaction time"), so for a dialog where the operator replied to the client only once (for example, a single email or a call), the value does not exist, but it looked like "0 seconds". Now "—" is shown in that case. This also applies to old dialogs — the data itself has not changed or been lost. The card description now explains how the average is calculated.

## Fast Line Pro

**Fixed**

- **Adding a segment to a knowledge base on Dify v2 works again.** On instances with Dify v2, manually adding a segment to a knowledge base document ended with a "service unavailable" error, and a segment without an index was left in the document: it appeared in the list, but search could not find it. Now the segment is added and indexed, and search finds it. Behavior on Dify v1 has not changed. If failed attempts left segments in a document that search cannot find, delete them and add them again.

## Please note

- **The "Average chat reaction time" column now shows "—" instead of "0".** On all instances with native statistics, "—" will also appear in old dialogs: this marks dialogs where the operator did not reply to the client a second time. This is not data loss. When sorting ascending, rows with "—" come first, and in CSV/XLSX exports such cells are empty rather than 0. If you used this column in your own calculations, note that the zeros are now empty.

## Related documentation

- [Release 5.17.1 notes](/en/releases/5.17.1.md)
- [Use an action in a scenario](/en/scenariobuilder/how-to/use-action-in-scenario.md)
- [Duration and reaction time metrics](/en/statistics/how-to/view-appeals-duration-and-reaction-metrics.md)
- [Configure knowledge base segments](/en/fastlinepro/how-to/configure-segments.md)