Release 5.8.9

What Changed

  • Operator Line: fixed a dialog auto-distribution issue — fully idle operators are back in the pool and receive new chats instead of all chats piling on one already-busy operator.
  • Chat widget: pasting text copied from Word, Excel, Google Sheets, or code editors no longer inserts stray formatting artifacts; pasting an image from the clipboard now attaches it like a regular file.
  • Scenario Builder: clicking a step highlights its incoming and outgoing connections; after a test run, the exact path the scenario took through branches is now highlighted too.
  • Broadcasts: when some selected clients have no contact for the chosen bot, the send modal now explains why and shows how many recipients will actually be reached.
  • Tickets and chats: the Update record scenario step now closes the dialog when the target status is a closing status, matching how manual closing works.
  • Bot scenarios: a failed "Send sticker" step is now logged and can follow an error connection instead of silently continuing.
  • FileManager: upload status badges (Pending / Completed) are now translated in every supported interface language.

How It Changed

Operator Line — dialog distribution

Before: an operator who just came online or closed all their dialogs (0 active chats) could become invisible to distribution for their skill group — new dialogs kept going to operators who already had chats open, while free operators sat idle and the queue grew.

Now: fully free operators participate in distribution again, on equal footing with everyone else; a new dialog goes to the least loaded matching operator, as intended.

Chat widget — paste behavior

Before: pasting text copied from rich-text sources (Word, Excel, Google Sheets, code editors) could send the message with leftover formatting code in front of the actual text. Pasting a screenshot or image from the clipboard did not work as a regular attachment.

Now: pasting text keeps only the plain text, wherever it was copied from. Pasting an image from the clipboard attaches it the same way as selecting a file — with a preview, the option to cancel, and the usual size limit.

Scenario Builder — edge highlighting

Before: clicking a step gave no visual feedback about its connections, and after a test run you could only see which steps had executed (checkmarks), not which branch of an if/switch condition the scenario actually took.

Now: selecting a single step highlights its incoming connections in green and outgoing connections in orange. After a debug/test run, the connections the scenario actually traversed are highlighted, making it easy to see exactly which branch was taken in a condition.

Broadcasts — contact warnings

Before: if a selected client had no contact registered for the bot chosen for a broadcast, the channel list in the send modal was simply empty, with no explanation. When only some of the selected clients lacked a contact, they were silently dropped from the recipient count.

Now: the send modal explains why the channel list is empty (for example, that the bot may have been deleted) and, when only part of the selection is unreachable, shows a clear breakdown of how many recipients will and will not receive the broadcast before you send it.

Tickets and chats — closing via Update record

Before: the Update record scenario step could change a dialog's status name, but did not close the dialog the way the Operator Line UI or an explicit "resolve" action does — a dialog assigned a closing status could stay open.

Now: when Update record sets a status marked as a closing status, the dialog is closed the same way as manual closing (operator unassigned, removed from the queue). Statuses that only mark a ticket resolved without closing the dialog keep working as before.

Why It Matters

Operators get an even, predictable share of incoming dialogs instead of overload on a few agents while others wait idle — fewer chats stuck in queue and faster first response. Clients using the chat widget no longer send messages cluttered with formatting artifacts, and can share screenshots directly by pasting them. Scenario authors debug branching logic faster by seeing the exact path a test run took. Marketers know the real reach of a broadcast before sending it instead of discovering gaps afterward. Scenario authors relying on Update record to close dialogs get the behavior they expect, and a failed "Send sticker" step can now be handled explicitly instead of failing silently.