--- title: "Release 5.14.3" description: "Operator Line folder counters, filters, table columns, and mass actions all report the real numbers again, a client's first message after a closed chat reaches the operator, and Scenario Builder lets you clean up duplicate node IDs yourself." --- # Release 5.14.3 This release is about Operator Line telling you the truth: folder badges show the exact number of appeals instead of a number capped by what is loaded on screen, filters from the standard form stop being rejected or quietly returning the wrong set, client and organization columns in the table view fill in again, and the "Send message" mass action addresses exactly the appeals you have in front of you. Alongside that, a client who writes after an operator closed the chat no longer has their first message swallowed, and Scenario Builder finally lets you see and delete a duplicated node instead of having one silently disappear from the canvas. ## Operator Line **Fixed** - **Folder counters show the exact number of appeals.** On instances that still read appeals the classic way, the badge next to a folder in the left menu — "Unassigned", for example — counted only the appeals already loaded into the current window, so it could disagree with the total shown in the list header. Folder badges now show the real total, they update as new messages, transfers, and closures arrive, and a folder that had no badge until you opened it gets one right away. Expanding a group fills in exact totals for its items too. - **Filters built in the standard form work again.** A filter assembled in the standard Operator Line filter form could be rejected outright, or silently return the wrong appeals, because some of its conditions are not offered in the custom condition builder. Those filters are accepted again. In addition: filtering by skill group follows the current link between groups and topics; dialog type, "has a reply", and "closed by timeout" behave the way they did before; the **No topic** option now really means "no topic" instead of matching a topic with ID 0; and a filter with no status chosen keeps the usual scope of open appeals instead of mixing closed ones in. - **Client and organization columns fill in inside the table view.** Dynamic client columns in the Operator Line table view could show up empty even though the client card had the value. They now read from the current client record, organization columns use the client's actual organization and fill in its name and custom values, and the values survive a global text search. A table that is already open loads the values for newly selected columns without a reload. - **The "Send message" mass action matches the current folder and filter.** The count of affected appeals, and the recipients the message actually went to, could differ from what the folder and applied filter showed on screen. The mass action now works over exactly the appeals in your current view. - **A client's first message after a closed chat reaches the operator.** After an operator closed a chat, the client's next message could disappear instead of opening a new appeal — often only the second message got through, and attempts to reopen produced empty appeals with old text. This affected dialogues that an operator had started, chats an operator re-joined after closing, and dialogues that began from a welcome message. Those dialogues now behave like any other: one message after the close opens a new appeal with that text, and the closed appeal stays closed. See **Please note** below for a scenario setting that some bots also need. ## Scenario Builder **Fixed** - **Duplicated nodes can now be cleaned up from the canvas.** A scenario section could end up with two nodes sharing the same ID — for example after cloning a bot. Only one of them was drawn, its twin and their connections vanished silently, the inspector opened the wrong one, and deleting by that ID removed *both* nodes at once, which is how a live scenario could lose a **Wait for input** node and start sending clients straight to an operator. Opening such a scenario now shows both nodes, with the extra one marked **Copy of id X**, a message explaining what to do, and an entry in the validation panel with a **Delete copy** button that removes only that copy and its own connection. Saving a scenario that still contains duplicate IDs is refused with a message naming the sections and IDs involved, and a connection that cannot be made now names the node it actually leads to. Nothing is written to the scenario until you save it yourself, and bot behavior does not change until then. ## Please note - **Some bots need a scenario change on top of this release.** The fix above restores the transition after a chat is closed for dialogues where the setting was never recorded. A **Connect to operator** node that has **Enable transition on chat close** explicitly turned off still keeps it off, by design — that has been the behavior since 5.13.2. If clients on a particular bot still cannot get through after a close, check that option on the bot's connect nodes. - **Restoring an older scenario version that contained duplicated IDs.** Both nodes are kept — nothing is lost, which is the point of the fix — but the copy comes back as an ordinary node with its own ID and no **Copy** marker. Nothing points to it, so it never runs; it shows up in the validation panel as an unused block and you can delete it. Before this release, restoring such a version quietly lost the node. ## Related documentation - [View the request queue](/en/operatorline/how-to/view-request-queue.md) - [View the chats table](/en/operatorline/how-to/view-chats-table.md) - [Manage folders](/en/operatorline/how-to/manage-folders.md) - [What are filters](/en/operatorline/explanation/what-are-filters.md) - [Create a filter](/en/operatorline/how-to/create-filter.md) - [Find appeals with global search](/en/operatorline/how-to/search-appeals-globally.md) - [Connect a chat to an operator](/en/operatorline/explanation/connect-chat-to-operator.md) - [Configure skill groups](/en/settings/how-to/configure-skill-groups.md) - [Configure subjects](/en/settings/how-to/configure-subjects.md) - [Connect to operator node](/en/scenariobuilder/explanation/connect-to-operator-node.md) - [Connect to operator parameters](/en/scenariobuilder/reference/operator-panel-connect-parameters.md) - [Edit a scenario](/en/scenariobuilder/how-to/edit-scenario.md) - [Find nodes on the canvas](/en/scenariobuilder/how-to/find-nodes-on-canvas.md) - [View scenario history](/en/scenariobuilder/how-to/view-scenario-history.md)