2026 Commerce Search Service release notes
7 min
Subscribe to updates on this page using the notification and RSS feed options.
October 15
Version 1.0.14
Enhancement
- Improved security.
Bug fixes
- Fixed an issue where long-polling operations could fail when using cached clients that had been evicted after expiration.
- Fixed an issue when creating a Serving Control where the first typed character could be removed.
September 21
Version 1.0.13
Enhancements
- Reduced Search Service log noise in Sandbox, Demo, and Production environments, which surfaces real warnings and errors faster.
- Improved security.
Bug fixes
- Fixed the issue where Search Service memory grew steadily under sustained workloads and never returned to baseline. Search now stays responsive during long-running indexing and query loads.
- Fixed the issue where Search Service leaked connections when a cached client was discarded while still starting. Connection use no longer climbs after credential rotation.
- Fixed the issue where saving a Linguistics Controls trigger with Browse Categories selected returned an internal server error. Commerce Search now disables Browse Categories for control types that do not support it.
- Fixed the issue where the Submit button stayed disabled in the Create Serving Config dialog, blocking new serving configs.
- Fixed the issue where a control failed to save after you entered Page Categories and then switched to Search.
August 18
Version 1.0.12
Enhancement
- Restyled the Commerce Search v3 admin screens to match the current Optimizely design. The Serving Configs and Serving Controls pages now look consistent with the rest of the Admin Console. See Configure Commerce Search v3 controls for information.
- Improved Commerce Search v3 availability so search keeps serving when a supporting cache or secrets service is briefly unavailable.
Bug fixes
- Fixed the issue where deleting a product that no longer exists returned an error during Commerce Search v3 bulk indexing. Delete requests for missing products now return a 404 response without generating an error log.
- Fixed the issue where the Start Date and End Date fields under Applicable Time Ranges could not be edited. The fields now accept input when you create or edit a serving control.
- Fixed the issue where editing a serving control on the Serving Controls page opened an empty form. The form now loads the saved control values.
- Fixed the issue where editing a serving configuration on the Serving Configs page opened an empty form. The form now loads the saved configuration values.
June 11
Version 1.0.10
Enhancement
- Improved security.
May 14
Version 1.0.9
Enhancements
- Increased the Commerce Search v3 facet value limit from 50 to 300, so shoppers see the full range of filter options instead of truncated lists when attributes have many values. Static attribute filters now return up to 300 values; dynamically generated facets remain limited to 50. See Limitations of Commerce Search v3 for details.
- Improved security.
March 26
Version 1.0.8
Enhancements
- Improved security.
- Updated the Autocomplete API and Search API to handle "429 Too Many Requests" rate limit errors gracefully when using Commerce Search v3.
Bug fix
- Fixed an issue where there were unhandled errors and search performance issues when logged in customers used search.
March 5
Version 1.0.7
Enhancement
- Improved security.
Bug fix
- Fixed an issue where the Serving Controls page only listed up to 50 controls. The default limit has now been increased to 1000.
February 12
Version 1.0.6
Enhancements
- Added support for N‑gram tokenization for part number-related fields.
- Improved security.
January 15
Version 1.0.5
Enhancements
- Enhanced the Search Service Authorization logic to retrieve and verify instance permissions using Commerce Product Instance details. This helps simplify and improve the permissions validation.
- Updated the User Events sync to work across all regions.