---
title: "Release 5.4.1"
description: "Find a conversation by typing just a dialog or ticket number, send large Outlook emails more reliably."
---

# Release 5.4.1

> **In short:** You can now find a conversation by typing only its number.
> Large Outlook emails reach customers more reliably, and scenario authors
> get a more stable Wait for Input step.

## For operators

**New**
- Find a conversation by number — type only digits and the system locates the dialog by its internal number or ticket number. The list shows which match was used.

**Improved**
- Large Outlook emails (long body or attachments) are sent more reliably — fewer failures caused by request size limits.
- Refreshed welcome and settings screens in the Constructor now look consistent with the rest of the interface.

## For administrators and scenario authors

**New**
- Field hints in the Wait for Input step make it clearer what each setting does.

**Improved**
- The Wait for Input step keeps all settings (message text, extra fields, slow mode) when scenarios are imported or exported.

## What this means for your team

- Operators find a conversation in 1-2 seconds when a customer gives only a ticket number — no extra search needed.
- Fewer failed deliveries for large emails through corporate mail.
- Scenarios with the Wait for Input step move between environments without manual cleanup.

## Related documentation

- [What the Wait for Input node is](/en/scenariobuilder/explanation/wait-for-input-node.md)
- [Wait for Input node parameters](/en/scenariobuilder/reference/wait-for-input-parameters.md)
- [How to view conversations in a table](/en/operatorline/how-to/view-chats-table.md)
- [How to configure the instance (email provider)](/en/settings/how-to/configure-instance.md)