Hi Bill,
Yes, this is expected behavior to some extent. Zero-Downtime Deployment (ZDT) does not support every type of model change. Mendix only allows specific configuration changes and compatible model changes to be deployed without downtime.
According to the current Mendix documentation, the following model changes are compatible with ZDT:
Microflows, except changes to their parameter type, parameter count, or parameter name.
Model folders.
Image data of ImageCollections.
Images of entities.
UserRole and ModuleRole description text.
Custom error messages for parent/child association delete behavior.
Model version changes.
Why does adding a Create Variable action disable ZDT?
There is an important distinction here: if the variable is created inside a microflow, the current documentation lists microflow changes as ZDT-compatible, provided the microflow's parameters are not changed.
Therefore, if adding only a Create Variable action disables ZDT, I would not assume this is the intended limitation. Check the following:
Confirm that the application is running Mendix Runtime 10.24 or later.
Review the complete model changes included in the deployment package, not just the Create Variable change.
Verify whether any other unsupported model elements or database structure changes are included.
Create a test branch and make only one microflow change (add a Create Variable action without changing its parameters).
Create a deployment package and check whether the ZDT option becomes available.
If the option is still disabled with only this microflow change, I recommend raising a ticket with Mendix Support and sharing the deployment package details and model change comparison. This will help determine whether the deployment eligibility check is behaving incorrectly.
My recommendation: Use ZDT for supported configuration changes and compatible model changes. For unsupported model changes, use the standard deployment process.
Official documentation:
https://docs.mendix.com/developerportal/deploy/zero-downtime/
Hope this helps! If you find this answer helpful, please mark it as the accepted answer.
Hi,
From my understanding, Zero Downtime Deployment is intended to support deployments that include compatible model changes, not just configuration changes. However, certain model changes or unsupported deployment scenarios may cause the option to become unavailable.
I would suggest checking whether the model changes introduce any database schema modifications or other changes that are not supported by Zero Downtime Deployment. Also, verify the deployment compatibility requirements for your Mendix version.
It would be helpful to check whether the same issue occurs with a simple model change in a test environment.
Hope this helps!
Hi Bill,
You’re right that the docs allow some model changes. ZDT supports configuration-level changes or compatible model changes, and the compatible list is short. It includes microflows, except for changes to their parameter type, parameter count or parameter name, plus folders in the model, ImageCollection image data, entity images, user role and module role descriptions, and custom delete-behavior error messages.
Anything else in the new package switches the deployment to a standard restart. That includes domain model or database changes, pages, nanoflows, Java actions and widgets, and runtime upgrades.
So a single “Create variable” inside a microflow should qualify. When it doesn’t, the cause is usually one of these:
The package is compared with what is currently running, not with your last commit. Every change since the last deployment to that environment counts. If an earlier commit changed a page, an entity or a nanoflow and it hasn’t been deployed yet, ZDT is disabled.
The runtime versions differ. ZDT requires Mendix Runtime 10.24 or above, and a runtime upgrade always needs a standard restart. If the new package was built with a different Studio Pro patch (for example 11.12.6) than the one the environment is running, that counts as a runtime upgrade.
Studio Pro changed other files in the package. Opening the app in a newer Studio Pro patch, updating a Marketplace module, or rebuilding the theme or widgets can change files you didn’t edit yourself. Check the Changes pane or the commit diff before building.
The microflow’s parameters changed. Changing a parameter’s type, count or name makes the change incompatible.
How to confirm:
Deploy the current revision once with a standard restart, so the environment matches your branch.
Change only the body of one microflow (no parameter changes), commit, and build a new package from that revision with the same Studio Pro version.
Open the Deploy Wizard and check the Deploy without downtime option on the Other Options tab. The first deployment of an environment always behaves like a regular one. ZDT applies from the next deployment onward.
If the option is still disabled after a clean microflow-only change, the behavior contradicts the documentation. In that case, raise a ticket with Mendix Support and include both package versions and the environment name.
Hope this helps! If this solution works for you, kindly mark it as the accepted answer so it can help others facing the same issue.
Thanks everybody for the responses, but has anyone actually tried? I've tested several "compatible" changes and none of them work. The only time I get the ZDT option is when I change a Constant or Scheduled Event setting from within sprintr. I haven't been able to successfully get the option to show up after a commit. I'm on 11.12.6 currently.