From 6b46b695e00ea1af72947485d4fabe2e3f51c0ad Mon Sep 17 00:00:00 2001 From: Akhil Krishnakumar Date: Tue, 29 Sep 2026 17:56:28 +0200 Subject: [PATCH 1/3] Add Zero Downtime model compatibility list --- .../mendix-cloud-deploy/zero-downtime.md | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md b/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md index 156432b2c8f..17503e479c0 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md @@ -61,9 +61,20 @@ Examples of changes that qualify for ZDT include: * Adjusting log-level settings * Changing resource limits, such as CPU or memory allocation * Rotating credentials or API keys -* Other configuration updates made directly through the Cloud Portal +* Other configuration updates made directly through the Cloud Portal. During these types of updates, Mendix Cloud performs the deployment in a way that keeps your environment continuously available. +#### Model Change that are compatible with ZDT {#zdt-compatibility} + +* Microflows, except for changes to their parameter type, parameter count or parameter name +* Folders (in the model) +* Image data of ImageCollections +* Image of an Entity +* UserRole description text +* ModuleRole description text +* Custom error messages configured for the delete behavior of parent/child associations +* Model Version + ### When ZDT Does Not Apply Zero-downtime deployment will not apply under the following conditions: @@ -71,6 +82,7 @@ Zero-downtime deployment will not apply under the following conditions: * Mendix Runtime versions below 10.24 * Upgrading to a new Mendix Runtime version * Deploying a new MDA (application model update) + * Any changes that are outside the [above mentioned list](/developerportal/deploy/zero-downtime/#zdt-compatibility) * Changes involve database structure updates For these scenarios, the Cloud Portal will display the standard restart message before deployment. From 4a739be795b593735c576894359e1a47a50ef263 Mon Sep 17 00:00:00 2001 From: Olufunke Moronfolu Date: Fri, 2 Oct 2026 16:18:19 +0200 Subject: [PATCH 2/3] Update: model changes compatible with ZDT --- .../deployment/mendix-cloud-deploy/zero-downtime.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md b/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md index 17503e479c0..d6bac3ab33f 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md @@ -62,15 +62,18 @@ Examples of changes that qualify for ZDT include: * Changing resource limits, such as CPU or memory allocation * Rotating credentials or API keys * Other configuration updates made directly through the Cloud Portal. + During these types of updates, Mendix Cloud performs the deployment in a way that keeps your environment continuously available. -#### Model Change that are compatible with ZDT {#zdt-compatibility} +#### Model Changes Compatible with ZDT {#zdt-compatibility} + +The following model changes are compatible with ZDT: * Microflows, except for changes to their parameter type, parameter count or parameter name * Folders (in the model) * Image data of ImageCollections * Image of an Entity -* UserRole description text +* UserRole description text * ModuleRole description text * Custom error messages configured for the delete behavior of parent/child associations * Model Version @@ -81,8 +84,7 @@ Zero-downtime deployment will not apply under the following conditions: * Mendix Runtime versions below 10.24 * Upgrading to a new Mendix Runtime version -* Deploying a new MDA (application model update) - * Any changes that are outside the [above mentioned list](/developerportal/deploy/zero-downtime/#zdt-compatibility) +* Deploying a new MDA with changes outside the [model compatibility list](/developerportal/deploy/zero-downtime/#zdt-compatibility) * Changes involve database structure updates For these scenarios, the Cloud Portal will display the standard restart message before deployment. From 84de4910bb9c64a222354d121f91548ebe5c2366 Mon Sep 17 00:00:00 2001 From: Olufunke Moronfolu Date: Fri, 2 Oct 2026 16:26:08 +0200 Subject: [PATCH 3/3] Update: include compatible model changes in ZDT prerequisites --- .../en/docs/deployment/mendix-cloud-deploy/zero-downtime.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md b/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md index d6bac3ab33f..b2ceb8bea27 100644 --- a/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md +++ b/content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md @@ -19,7 +19,7 @@ With ZDT, Mendix Cloud intelligently manages the deployment process, ensuring yo To leverage the benefits of zero-downtime deployment, your Mendix application and deployment environment must meet the following criteria: * **Mendix runtime version** – Must be running on Mendix Runtime version 10.24 or above. -* **Change type** – The deployment must involve only [configuration-level changes](/developerportal/deploy/zero-downtime/#zdt-application). +* **Change type** – The deployment must involve only [configuration-level changes](/developerportal/deploy/zero-downtime/#zdt-application) or [compatible model changes](/developerportal/deploy/zero-downtime/#zdt-compatibility). {{% alert color="info" %}} No special setup is required to enable ZDT. When your application and deployment meet these prerequisites, ZDT is automatically available for eligible changes. @@ -30,7 +30,7 @@ No special setup is required to enable ZDT. When your application and deployment {{< figure src="/attachments/deployment/mendix-cloud-deploy/zero-downtime/zdt-process-success-flow.png" alt="Sequence diagram illustrating the Zero-Downtime Deployment process, showing the Technical Contact initiating deployment, Mendix Cloud starting a new app version in the background while the current version serves users, the new version preparing configuration and reporting ready, Mendix Cloud gracefully stopping the old version, and finally directing traffic to the new version without user interruption." >}} -When an eligible configuration change is deployed with ZDT, Mendix Cloud orchestrates the following steps: +When an eligible change is deployed with ZDT, Mendix Cloud orchestrates the following steps: 1. **Initiate deployment** – The Technical Contact triggers deployment with **Deploy without Downtime** in Mendix Cloud. 2. **Current version active** – The existing application version continues to serve all user traffic without interruption.