Release 5.8.2

What Changed

  • Operator Line: the chat list stays responsive with many active dialogs and frequent incoming messages — without UI freezes.
  • Instagram: replies to a Story no longer open a second parallel chat; replies sent from the native Instagram app appear in the operator dialog again.
  • Tickets (email): you can create an email request only on a bot with a configured mailbox — the New ticket form hides unsuitable channels.
  • Operator Line — return visits: after a closed chat, the client sees the continuation of the previous conversation, not an empty dialog; queued chats no longer disappear after a few seconds; unwanted operator auto-connect after close stops when the scenario disables it.
  • Scenario Builder: template actions stay in sync between the new editor and classic Dialog — the scenario runs with up-to-date parameters; Version history shows the correct date and ID for the selected version.

How It Changed

Before: With hundreds of active dialogs and frequent messages, the chat list could lag. An Instagram Story reply sometimes opened two chats at once. Client replies from the native Instagram app could be missing in Operator Line. An operator could pick an email channel for a bot without a mailbox and hit a system error on send. A return visit could show a new empty dialog in the queue; a chat could briefly vanish from the queue; an operator could auto-connect several times in a row without a new client message. Mixed editing in both scenario editors could leave action parameters out of sync. The version comparison modal showed Invalid Date and an empty ID.

Now: Chat list updates are incremental instead of rebuilding the full list on every message. Story replies route to a single chat with history. Instagram echo messages are delivered to the dialog. In New ticket, email is available only for bots with mail configured; attempts to bypass the guard return a clear message. On return visits the most recent closed dialog is reactivated with full history; the queue is stable for scenarios with a wait cascade; auto-connect after operator close happens only where the scenario explicitly allows it. Template action parameters sync on save and load. Version history shows correct metadata even when the opened version is not on the first page of the list.

Why It Matters

Operators work faster in the queue during peak load and keep conversation context. Instagram requests land in one chat without duplicates or drops. Administrators avoid creating unusable email tickets on unprepared bots. Repeat client contacts behave predictably — with history and a stable queue. Integrators can safely combine Scenario Builder and the classic editor, and version comparison gives accurate information for change audits.