diff --git a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md
index ec57a14cb72..855f60a830e 100644
--- a/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md
+++ b/content/en/docs/deployment/private-cloud/private-cloud-cluster/_index.md
@@ -549,7 +549,7 @@ Starting from Mendix Operator 2.23.0, environments running in `leaderless` mode
 When another **runtimeLeaderSelection** mode is used (default, unspecified `assigned` mode, or `none`), the healthcheck microflow is used, as described above.
 {{% /alert %}}
 
-#### Customize Liveness Probe to Resolve Crash Loopback Scenarios
+#### Customize Liveness Probe to Resolve Crash Loopback Scenarios{#customize-liveness}
 
 The `liveness probe` informs the cluster whether the pod is dead or alive. If the pod fails to respond to the liveness probe, the pod will be restarted (this is called a `crash loopback`).
 
diff --git a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md
index fe03b95f711..9d9452920e7 100644
--- a/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md
+++ b/content/en/docs/refguide/modeling/app-explorer/app/app-settings/runtime-tab.md
@@ -40,7 +40,7 @@ This setting was introduced in Mendix 11.6.3.
 
 If this option is enabled, Web (both React and Dojo) and Native Mobile clients will be able to handle both `empty` and empty string `''` values for `String` attributes. <br>
 
-If this options is disabled, `String` attribute values on the client-side will always contain only the `''` value to represent empty state. `empty` values will be automatically converted to `''` when transfered to the client-side. 
+If this options is disabled, `String` attribute values on the client-side will always contain only the `''` value to represent empty state. `empty` values will be automatically converted to `''` when transferred to the client-side. 
 
 For a detailed explanation, see the *Empty Strings Handling* section of [Upgrading from Mendix Studio Pro 10 to 11](/refguide/upgrading-from-10-to-11/#empty-strings-handling).
 
@@ -89,9 +89,17 @@ Applications deployed to the cloud will use this setting to select which Java ve
 You can select a microflow that is automatically run immediately after the application has been started up.
 
 {{% alert color="warning" %}}
-There is a timeout of 11 minutes on the after startup microflow. If your after startup microflow takes longer than 11 minutes, your whole app will fail to start.
-
 After startup is designed to initialize the app and therefore runs before the app is able to respond to incoming service requests (for example, published REST services).
+
+There is a timeout set on the after startup microflow. If your after startup microflow exceeds this, your whole app will fail to start. The duration of this timeout will depend on the environment you are deploying to. The table below lists the timeouts for common deployment options.
+
+| Deployment Target | Timeout | Comment |
+| --- | ---: | --- |
+| Mendix Cloud | 15 minutes | This can be changed—contact [support](https://support.mendix.com/) |
+| Cloud Foundry | 11 minutes | Also for older Mendix versions running on Mendix Cloud |
+| Mendix on Kubernetes | Configurable | See [Customize Liveness Probe](/developerportal/deploy/private-cloud-cluster/#customize-liveness) for more information
+| SAP BTP | 60 seconds | This is [configurable](/developerportal/deploy/sap-cloud-platform/#DeployPackage) |
+
 {{% /alert %}}
 
 ### Before Shutdown