---
title: 2026 Mission Control release notes
slug: configured-commerce/release-notes/2026-mission-control-release-notes
docTags: 
createdAt: 2026-08-18T12:29:50.000Z
---

Subscribe to updates on this page using the notification and RSS feed options.

## 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](docId\:DBU3AI8-rxF10qu5Hbf_s).
- **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](docId\:JzvnQh1vW9RkoAY7rgWmK) 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](docId\:DBU3AI8-rxF10qu5Hbf_s).
- **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.

:::hint{type="info"}
**Note**

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](docId:5TbcT84El3pBYOBORO17Z) for information.
:::