---
title: "Release 5.8.5"
description: "Process search and pinning in the Constructor main menu; Time in Status trigger for Operator Line chats."
---

# Release 5.8.5

## What Changed

- **Constructor:** the **Process menu** block now includes **name search** and **star pinning** for frequently used processes.
- **Scenario Builder:** the **Time in Status Exceeded** start-step trigger lets you choose entity type **Chat** — automation for regular Operator Line dialogs, not only tickets.

## How It Changed

### Constructor

**Before:** you picked the active process from a long dropdown with no search; every process appeared in a fixed order, which was hard to scroll on large instances.

**Now:** click the field with the current process name to open a panel with **Process search** and the list. The star on the right **pins** a process (it does not switch the active one); pinned processes appear at the top. Pin settings are saved in your browser per user.

### Scenario Builder

**Before:** the **Time in Status Exceeded** start-step trigger worked only for **ticket** requests.

**Now:** in **Entity type** you can choose **Chat** or **Ticket**. For chats, the scenario runs when a dialog stays in the selected status longer than the configured time — for example, to auto-close an inactive chat. Existing ticket scenarios keep working unchanged; for chats you must explicitly select **Chat** and publish the scenario.

## Why It Matters

Administrators and integrators switch between processes faster on large instances — favorite bots stay at the top without scrolling a long list. Integrators can build time-in-status automation for regular Operator Line chats without creating a separate ticket for every dialog.

## Related documentation

- [Switch the active process in the main menu](/en/constructor/how-to/switch-active-process.md)
- [Configure internal events for the start node](/en/scenariobuilder/how-to/configure-start-node-internal-events.md)
- [Internal events trigger parameter reference](/en/scenariobuilder/reference/internal-events-trigger-reference.md)