Release 5.16.1
A patch release about data accuracy and the reliability of everyday tools. In Scenario Builder, parallel section editing is more robust: a second tab of the same integrator no longer interferes with a section it does not own, and edits in a busy section are no longer lost on publish; separately, the "Assigned operator" field is saved again in the connect-to-operator node. In statistics and the quality dashboard, several distortions are fixed: the "Skill group" filter on the Subjects tab, the "Operator" filter that attributed dialogs to the system "Fastline AI", and quality dashboard metrics that only counted the first 1000 assessments. In the operator panel, we fixed message sending (a stuck "NaN" delay), silent notifications caused by the browser blocking sound, and an empty dialog close status. Fast Line Pro now shows a knowledge base segment indexing error directly, and a post forwarded to Instagram Direct no longer gets lost on the way to the operator.
Scenario Builder
Fixed
- Parallel section editing is more reliable. If you opened the same scenario in two tabs or on two devices under the same account, the second tab could silently interfere with a section the first tab held — and a request to edit from your own other tab could get lost without a trace. Now each tab is a distinct section owner: a second session of the same user goes through the same "Request editing" protocol as a colleague would (a dialog with "Hand over" / "Block" buttons, an auto hand-over if the owner does not respond). The canvas becomes editable only once the section lock for that specific tab is confirmed.
- Publishing no longer loses edits in a section someone else has taken over. If a colleague took over your section while you were editing it (on request, or after 3 minutes of inactivity), your saved changes could previously be discarded on publish. Such sections are now skipped with a warning and stay marked as changed — your edits are kept until the section is released.
- An idle section owner is now detected from real activity — cursor movement, selecting a node, panning the canvas, or typing — instead of relying only on the background presence signal. The rule "owner inactive for 3 minutes → the section is handed over without a request" now actually fires.
- Moving or copying nodes between sections locks both sections involved until publish, and the operation correctly cancels if someone else changes one of them in the meantime.
We recommend reloading already-open Scenario Builder tabs after upgrading to 5.16.1 — this applies only to instances with parallel section editing enabled.
- The "Assigned operator" field is saved again in the "Connect to operator" node. The selected operator was visible while the node panel was open, but reopening it or publishing the scenario returned an empty field. The same applied to the "Instagram: room type" field in the same node. Both fields now save and publish correctly.
- The default dialog close status is prefilled again in the new design. The "Exit" button in the chat header opened the close dialog with an empty status field, even though a status was marked "Default" in the dialog status settings — operators had to pick a status by hand every time. The field now fills in the same way it already did elsewhere in the close flow: the dialog's current closing status, or, if there is none, the status marked "Default".
Statistics
Fixed
- The "Skill group" filter on the Subjects tab now actually filters the data. The filter chip was visible, but the "Subjects" and "Subject / frequency" cards ignored it and always showed subjects for the whole instance. Both cards now respect the selected skill groups, consistent with the rest of the tabs.
- The "Operator" filter no longer attributes dialogs to the system "Fastline AI". If a bot briefly joined a dialog right after a human operator, the whole dialog and its rating could be attributed to "Fastline AI" instead of the real operator — filtering by a specific person showed almost no data. The operator of a dialog is now the last human participant who joined, and "Fastline AI" has been removed from the filter's value list. This fix is retroactive — figures for past periods where you filtered by operator may change (and become more accurate).
Quality Assurance
Fixed
- The quality dashboard now counts metrics across all assessments, not just the first 1000. On instances with a large volume of checks, the dashboard used to cap the data set at the 1000 most recent assessments — operators whose assessments fell outside that limit were missing from the metrics entirely. The same applied to the cards on the "My assessments" tab. Both screens now count all assessments matching the current filters.
- Pagination in the operators table on the dashboard now works. The next-page button and the rows-per-page switch used to have no effect.
- Dashboard filters are now applied with an "Apply filters" button, with a loading indicator, matching how the "Assessments" tab already works. This removes the guesswork when picking several filters in a row and protects against a stale response overtaking a newer request.
- "My assessments" — pagination and cards now count all of your assessments, not just the first 1000; sorting the table by dialog ID, checklist, and score now works.
Operator panel
Fixed
- Sending messages no longer gets stuck. For operators with a certain send-delay setting, the first Enter press showed a chip labeled "NaN" instead of a countdown and sent nothing — only a second Enter worked; the "Send" button could fail to send at all. The fix requires no action on your part.
- Notifications no longer go quietly silent. Browser policy blocks notification sound right after a page reload or opening a new tab, until you click or press a key in that tab — and the panel used to swallow this refusal without telling you. Now, right after the page loads, a banner reading "Notification sound is blocked by the browser" appears at the bottom of the screen with an "Enable sound" button; you can also unblock sound with any click, tap, or key press in that tab. The bell icon in the header now always reflects the real sound state.
- The message feed no longer stays empty because one stylesheet failed to load. In rare cases an operator's browser would refuse to load a single styling file (for example, because of antivirus software or a corporate filter), which made the entire message feed disappear even though messages were arriving from the server. Now such a failure no longer hides the feed: the stylesheet is requested again, and if that still fails, the operator sees a clear "Failed to load this part of the interface" message with a reload button — instead of empty space. The same applies to the dialog list and the details panel.
Fast Line Pro
Fixed
- A knowledge base segment indexing error no longer hides behind a plain "Disabled" label. If the knowledge base failed to index a segment (for example, because of a temporary technical issue), the interface used to show only that the segment was disabled, with no explanation. The segment list now marks such a row with an "Indexing error" badge showing the reason, and trying to save or enable a segment with an error shows a toast explaining why, without losing the text you already entered.
Fixed
- A post a client forwards in Direct no longer gets lost. The system could briefly mistake a post the client forwarded for a service message that precedes an ad-originated conversation, and never show it to the operator at all. Now, if no text arrives from the client within a few seconds after such a message, it is delivered to the operator as a regular message — with the post's media and its caption.