Release
Article MarkdownReport an error

Release 5.6.9

What's changed

  • Operator settings: fields validate in real time with clear error messages; user table sorts by role, manager, and schedule; duplicate file extensions are blocked; hot key conflicts are visible on the settings page.
  • Broadcasts: filters work more reliably; the system doesn't skip criteria; the old broadcast interface now recommends switching to the new constructor.
  • Stability: fixed a memory consumption issue that caused system instability.
  • OperatorLine: chat and contact details adapt to window size without horizontal scrolling; system messages are labeled correctly; long text is truncated with a tooltip on hover.

How it's changed

Before: Settings errors were not obvious; broadcasts could fail with filters; the system experienced instability under load; OperatorLine layout broke in narrow windows; system messages displayed incorrectly.

Now: Validation happens in real time; broadcasts process reliably; the system is more stable; layout adapts to window size; system messages are labeled correctly.

Why it matters

Operators find it more comfortable to configure their screens; broadcasts become a more reliable communication channel; the system runs without interruptions; operators are more comfortable working on screens of any size.

Details by product section

Settings — operator screens

Improved

  • Hot keys: conflicts appear on the settings page in real time; the error is visible when the first block is also open.

  • Session timeouts: the "Save" button is disabled if timeout is enabled but minutes are not set; validation happens live.

  • File management: the system warns when trying to add an extension that already exists; saving is blocked until extensions are normalized.

  • Users and roles: the user table sorts by displayed text (role name, manager name, schedule name); required fields are visually distinguished; user form shows * next to password in create mode; custom field types SELECT and SELECTAPI work; schedule remains visible even if the operator doesn't have access to calendars.

Broadcasts

Fixed

  • Contact filtering: the system no longer accepts invalid filter parameters; filters work correctly when selecting contacts by channel.

  • Temporal fail-fast: the system doesn't retry requests that contain SQL errors; deterministic errors (bad column name, syntax) are immediately treated as non-retryable.

  • Recommendation to switch to new constructor: the old broadcast interface shows a message about the more powerful new constructor with a link (if configured).

OperatorLine — chat and details

Improved

  • Layout in narrow windows: chat list, contact details panel, and request details adapt to window size without horizontal scrolling; long text is truncated with ellipsis.

  • Tooltips on hover: if text is truncated, the full text appears on hover (in contact details, requests, but not system messages).

  • System messages: chat list correctly displays system messages (for example, chat status changes) even when the payload doesn't contain explicit labels; instead of the sender's name, a "System message" label is shown.

Stability

Fixed

  • Fixed a critical issue that caused excessive memory consumption during intensive constructor and operator use.

Please note

  • The recommendation to use the new broadcast constructor is available if url_to_new_design is set in instance settings.

  • Tooltips in contact details can be selectively disabled for specific fields.

  • System messages in the older API might not have had explicit labels; the recognition algorithm is based on type, sender, and content.

Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request