Documentation
Docs
Learn
Release Notes
  • English
  • Українська
Docs
Learn
Release Notes
  • English
  • Українська
  • Release Notes
  • 5.6.10
  • 5.6.8
  • 5.6.7
  • 5.6.6
  • 5.6.5
  • 5.6.4
  • 5.6.3
  • 5.6.2
  • 5.6.1
  • 5.6.0
  • 5.5.6
  • 5.5.5
  • 5.5.4
  • 5.5.3
  • 5.5.2
  • 5.5.1
  • 5.5.0
  • 5.4.4
  • 5.4.3
  • 5.4.2
  • 5.4.1
  • 5.4.0
  • 5.3.42
  • 5.3.41
  • 5.3.40
  • 5.3.39
  • 5.3.38
  • 5.3.37
  • 5.3.36
  • 5.3.35
  • 5.3.34
  • 5.3.33
  • 5.3.32
  • 5.3.31
  • 5.3.30
  • 5.3.29
  • 5.3.28
  • 5.3.27
  • 5.3.26
  • 5.3.25
  • 5.3.24
  • 5.3.23
  • 5.3.22
  • 5.3.21
  • 5.3.20
  • 5.3.19
  • 5.3.18
  • 5.3.17
  • 5.3.16
  • 5.3.15
  • 5.3.14
  • 5.3.13
  • 5.3.12
  • 5.3.9
  • 5.3.6
  • 5.3.5
  • 5.3.3
  • 5.3.2
  • 5.3.1
  • 5.3.0
  • 5.2.14
  • 5.2.13
  • 5.2.12
  • 5.2.11
  • 5.2.10
  • 5.2.9
  • 5.2.5
  • 5.2.3
  • 5.2.2
  • 5.2.1
  • 5.1.1
  1. Docs
  2. /Release Notes
  3. /Release 5.6.10

Release 5.6.10

What Changed

  • Operator Line: after reopening a closed dialog, the close-reason label is preserved unless you clear it on purpose.
  • Scenario Builder: duplicate-alias warnings stay open until every conflict is fixed or you dismiss the dialog; the conflict list refreshes when the scenario changes.
  • Broadcast (V2): the counter for contacts excluded because they opted out of broadcasts shows the right number for filters and “send to all”; the operator log again records deferrals and skips caused by an active dialog.

How It Changed

Before: Reopening a dialog without changing the status label could wipe the close reason, which broke reports and history review. Clicking a conflicting alias in the warning closed the dialog even when duplicates remained; after deleting or renaming a node the conflict list did not always refresh. In Broadcast V2 the excluded-contact counter often showed zero for filtered campaigns; the operator log did not show deferrals and active-dialog skips the way the previous broadcast version did.

Now: The close reason stays after reopen until you explicitly clear it. The duplicate-alias warning only closes via the X button or when no conflicts remain; jumping to a node from the list no longer hides the dialog. The excluded-contact count matches contacts with broadcast opt-out; the log shows deferrals and active-dialog skips again.

Why It Matters

Supervisors and analysts keep close reasons after a dialog is reopened. Scenario authors see every duplicate alias until they finish fixing them. Broadcast teams plan audience reach more accurately and can explain why messages were deferred or skipped.

Product areas in detail

Operator Line — reopening a dialog

Fixed

  • When status changes from closed to another value (for example new), the close-reason label remains unless you submit a new value in the edit form.
  • To clear the label, submit an empty close-reason value when editing the chat.

Scenario Builder — duplicate aliases

Fixed

  • The duplicate-alias warning no longer closes when you click a row in the conflict list — you can visit every conflicting node in sequence.
  • The conflict list updates automatically after you delete, rename, or change nodes; when no duplicates remain, the dialog may close on its own or after you dismiss it.
  • Dismiss only via the X button or when there are no conflicts left.

Broadcast — audience and operator log (V2)

Fixed

  • In filtered campaigns and send to all mode, the counter for contacts excluded because they opted out of broadcasts shows the real total instead of always zero.
  • The operator log again shows entries when a message is deferred because the contact has an active dialog.
  • The log also shows skips during sending when the contact still has an active dialog — matching the previous broadcast experience.

Please note

  • Clearing the close reason after reopen is an explicit action in the chat edit form.
  • Alias warnings apply to Scenario Builder; review scenarios that reuse the same alias across sections.
  • Log improvements apply to Broadcast V2; delivery rules for who receives a message are unchanged.

Related documentation

  • Operator Line hub
  • Edit a scenario
  • View broadcast results
  • Check broadcast status
Prev
Release Notes
Next
5.6.8

On this page