Current short-term support hotfixes

  • Updated

This article contains a list of hotfixes for the current cloud release. Be aware that the most recent hotfix contains all previous hotfixes, so applying the latest hotfix automatically updates your environment to the current cloud release.

Optimizely has set a deadline for hotfix submissions each release to allow the Configured Commerce team time to prepare the upcoming release. See the hotfix submission deadline notice for more details.

Follow this article to receive email notifications when Optimizely Configured Commerce releases hotfixes for short-term support versions.

Current Cloud Release Version: 5.2.2608

Date Build Description
September 17, 2026 5.2.2608.665+sts
  • Added automatic fallback to Elasticsearch when Commerce Search v3 fails, so storefront search keeps working during an outage. See Limitations of Commerce Search v3 for more information.
  • Fixed the issue where an integration job never finished on sites that use Azure Storage.
  • Fixed the issue where products from a product information management (PIM) feed did not appear in Retail Search results. Indexing rejected products whose Basic Sale Start Date and Basic Sale End Date held placeholder values.
  • Fixed the issue where Classic CMS storefronts showed the browser's default 404 page instead of the site's error page. This affected .NET Core sites when a visitor requested a URL that does not exist.
  • Improved security.
September 16, 2026 5.2.2608.656+sts
  • Added an Admin Console message and a visual indicator for custom properties that have no stored value. This lets you tell an unset default from a value saved to the database. 
  • Fixed the issue where integration jobs stayed at InProgress and never finished. This affected .NET Framework 4.8 sites that use Amazon S3 file storage.
  • Fixed the issue where integration job debug logs were missing when the log source was set to Elasticsearch. These logs now appear regardless of the Log Debug Messages setting.
  • Fixed the issue where brand and product names ending in the letter y disappeared from search results and autocomplete. This happened when the name also contained a ®, ™, or © symbol.
  • Fixed the issue where a product recommendations carousel kept showing the previous page's products. This happened when the new page returned no recommendations.
  • Fixed the issue where sign-in pages still showed a single sign-on (SSO) option after it was disabled. The storefront and Admin Console now honor both Allow Sign in With OpenId Connect and Allow Sign in With Windows Account.
  • Fixed the issue where creating an account with a space in the user name failed with Microsoft.AspNetCore.Identity.IdentityError on .NET Core sites. Validation messages now show a readable description.
  • Improved security.