Skip to content

Commit fca14a2

Browse files
authored
Update zero-downtime deployment instructions
Clarified the eligibility criteria for zero-downtime deployment in the documentation.
1 parent 61dd896 commit fca14a2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

content/en/docs/deployment/mendix-cloud-deploy/zero-downtime.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ When an eligible configuration change is deployed with ZDT, Mendix Cloud orchest
4646

4747
By default, this option is off. In this state, your app will use the standard restart process during deployment. This default setting ensures stability and compatibility with existing application behavior.
4848

49-
Technical Contacts can decide whether to attempt a zero-downtime deployment by selecting the **Deploy without downtime** option on the **Other Options** tab when [deploying a package](/developerportal/deploy/environments/#deploy-wizard). If you select this option, Mendix Cloud will attempt a zero-downtime deployment, if your environment meets eligibility criteria.
49+
Technical Contacts can decide whether to attempt a zero-downtime deployment by selecting the **Deploy without downtime** option on the **Other Options** tab when [deploying a package](/developerportal/deploy/environments/#deploy-wizard). If you select this option, Mendix Cloud will attempt a zero-downtime deployment.
5050

5151
{{% alert color="info" %}}
5252
When a Technical Contact selects ZDT, the Cloud Portal displays a reminder to review any custom **before-shutdown** or **after-startup** microflows. This is crucial to ensure these microflows won’t cause conflicts during periods when two versions of your application might be running concurrently.

0 commit comments

Comments
 (0)