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.2606

Date Build Description
July 9, 2026 5.2.2606.529+sts
  • Fixed the issue where the Print button did not send an email on .NET 8 sites.
  • Fixed the issue where completing an order on .NET Core sites did not send an order event to Optimizely Data Platform (ODP).
  • Fixed the issue where partners could not run Admin.Api locally in development on .NET Core.
  • Fixed the issue where creating a restriction group with a customer rule skipped the Restriction step and then showed an unhandled error on the Summary step.
  • Added the Mobile Refresh Token Lifetime Minutes and Mobile Absolute Refresh Token Lifetime Minutes system settings on .NET Core, which let implementers control how long a mobile app stays signed in before a user must sign in again.
  • Fixed the issue where adding a new card in Saved Payments returned a 500 error for some payment gateways, such as Orbital and Payflow Pro.
  • Fixed the issue where a classic site on .NET Core threw an error when rendering a product list or product detail page that used a custom search engine optimization (SEO) view.
  • Fixed the issue where order history records were editable in the Admin Console on .NET Core sites, which let users save changes to completed orders. Order history fields are now read-only.
  • Fixed the issue where the nightly maintenance job could fail with an out-of-memory error on .NET Core sites that had a large backlog of records to delete. Batch deletes now run as set-based SQL deletes that honor the configured batch size and command timeout.
  • Fixed the issue where browsing a product list or product detail page on a classic .NET Core site returned a 500 error.
  • Fixed the issue where switching to a language that had no URL segment produced an inconsistent storefront home page URL.
June 29, 2026 5.2.2606.483+sts
  • Updated the Admin Console color scheme and logo to reflect Optimizely's current branding.
  • Fixed an issue where deploying a version upgrade could fail due to assembly load failures during startup. Assembly binding redirects now run earlier so upgrades deploy reliably.
  • Fixed an issue where an error was intermittently logged in the Application Logs after running an index with Commerce Search v3.
  • Fixed an issue on .NET Core storefronts where a user prompted to change their password received an internal server error (HTTP 500) after submitting a new password instead of being logged in.
  • Fixed an issue where Enable Nested Documents could not be configured for Commerce Search v1 or v2 when the global Search Indexer was set to Commerce Search v3. The setting can now be configured at the global level.
  • Fixed an unhandled error that occurred during checkout when a site was switched to Maintenance Mode. The maintenance page is now displayed correctly.
  • Improved security across the platform.