---
title: "Release 5.17.0"
description: "A continuation of the new search and filters work from release 5.16: building the search index is faster and lighter on the system, the migration page reports a more accurate status, and purging masked fields from the search index is now a reliable, visible process."
---

# Release 5.17.0

This release adds no new features — it continues the performance and reliability work on the new search and filters introduced in release 5.16. Building the search index after enabling or updating settings now finishes faster and with less load on the instance, the migration page reports a more accurate status, and purging masked fields from the search index has become a reliable, visible process.

## Settings: move to the new search and filters

**Improved**

- **The "Action needed" banner now appears only when there is something you can actually do from that page.** Previously the banner could ask for a technical step the instance owner could not perform — for example, a command only a ConnectiveOne engineer can run. Now, in those cases, the page shows a plain waiting state instead of an unmet demand, and an action button appears only when pressing it will actually do something.
- **Purging masked fields from the search index now shows real progress.** On large instances the process used to look "stuck" with no way to tell whether it was still running. It now confirms the start right away and reports actual progress through to completion; disk space freed by the purge is now reliably reclaimed.

**Fixed**

- **Fields marked "never store this value in search" could, in rare cases, briefly reach the search index** — right after the system started or during an index rebuild. These values no longer reach the index.
- **Attachment file names are now included in search matching and highlighting** for appeals with attachments, as originally intended.

## Stability and internal improvements

- Building and updating the search index for appeals with several client participants no longer processes the same appeal multiple times — indexing is substantially faster and lighter on the system.
- Changing an operator's or skill group's settings no longer recomputes every appeal that operator or skill group ever touched in the search index — on busy instances this could previously load the system heavily for no reason.
- The search index build now works in smaller batches, so it is less likely to delay other requests while indexing runs.

## Please note

- All changes in this release apply automatically to instances that already have the new search and filters enabled from release 5.16. No additional action is needed from an administrator.
- On instances where the new search and filters are not yet enabled, this release changes nothing.