diff --git a/modules/ROOT/pages/deploy-on-premises.adoc b/modules/ROOT/pages/deploy-on-premises.adoc
index 7eff59c299..be40961448 100644
--- a/modules/ROOT/pages/deploy-on-premises.adoc
+++ b/modules/ROOT/pages/deploy-on-premises.adoc
@@ -334,7 +334,8 @@ Updating a Mule application at runtime can be a complex change involving class m
 
 There are two ways you can update an application:
 
-* By adding the modifications over an existing unpacked app folder and touching the main configuration file (`mule-config.xml` located in the app's root directory by default).
+* By adding the modifications over an existing unpacked app folder and touching the main configuration file (`mule-config.xml` located in the app's root directory by default). +
+For this option to be valid, start the runtime with the system property `-M-Dmule.deployment.forceParseConfigXmls=true`.
 * By adding a new `jar` with an updated version of the app into the `$MULE_HOME/apps` directory. Mule detects the `jar` as an updated version of an existing application and ensures the update by a clean redeployment of the app. +
 Note that Mule discards any modifications to the old application folder. The new app folder is a clean unpacked application from a `jar`.