---
title: "Release 5.6.10"
description: "Close-reason labels stay after reopening a dialog; duplicate-alias warnings in Scenario Builder persist until resolved; Broadcast V2 shows correct excluded-contact counts and operator log entries for deferrals and active-dialog skips."
---

# 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](/en/operatorline/operator-hub.md)
- [Edit a scenario](/en/scenariobuilder/how-to/edit-scenario.md)
- [View broadcast results](/en/broadcast/how-to/view-broadcast-results.md)
- [Check broadcast status](/en/broadcast/how-to/check-broadcast-status.md)