2026 Mission Control release notes

  • Updated

Follow this article to receive email notifications when new releases are available for Optimizely Configured Commerce Mission Control.

April 2

  • Reduced database backup timeout – Database backups requested through Mission Control now expire after 24 hours in order to improve data security. 
  • Extension Script failures now post on the Dashboard and Notification views – If an extension script fails the deployment, it is now reported in Mission Control through the Dashboard and Notifications views. See Build and deploy notifications.
  • New approval process for partners requesting customer access in Mission Control – Introduced a new approval process that involves submitting a support request to reduce friction around implementation partners gaining access to customer environments in Mission Control.

March 13

  • Improved build and deploy notifications – Build and deploy failure emails and Mission Control notifications now differentiate between deployment failures and build failures, so administrators know exactly where the process failed. See Build and deploy notifications.
  • Added concurrent deployment handling – When a new commit triggers a deployment, Mission Control now checks for any active Configured Commerce deployments running on the given instance and terminates them before running the newly requested deployment.

These above enhancements are available for only Configured Commerce instances using the v2 build service. Upgrading to v2 is a simple, no-code process that provides additional performance and reliability benefits. See Build service v2 for information.