Apr 3, 2025 · Apr 3, 2025 · Apr 3, 2025
diff --git a/_docs/promotions/product-releases.md b/_docs/promotions/product-releases.md
 {: .table .table-bordered .table-hover}
 | Environment Status     | Description           |
 |------------        |---------------------------------------|
 | **Successful**     | Promotion to an environment is considered successful when the following conditions are met, in the order listed. {::nomarkdown}<ol><li>Pre-Action Workflow completed successfully.</li><li>Promotion Action submitted successfully. For PRs, the PR was successfully merged.</li><li>Application synced to the cluster.</li><li><li>Application is healthy.</li><li>Post-Action Workflow completed successfully.</li></ol>{:/}.    |
 | **Successful**     | Promotion to an environment is considered successful when the following conditions are met, in the order listed. {::nomarkdown}<ol><li>Pre-Action Workflow completed successfully.</li><li>Promotion Action submitted successfully. For PRs, the PR was successfully merged.</li><li>Application synced to the cluster.</li><li>Application is healthy.</li><li>Post-Action Workflow completed successfully.</li></ol>{:/}.    |
 | **Running**        | At least one step in a Pre- or Post-Action Workflow in the environment is currently in progress.  |
 | **Suspended**        | One or both the Pre- and Post-Action Workflows or the Promotion Action is pending execution. This could be because of a condition in the Workflow or because a pull request is pending manual approval.  |
 | **Failed**         | At least one step in a Workflow failed to execute, has a syntax error, was manually terminated, or the application is out of sync or degraded. |
diff --git a/_docs/promotions/promotion-flow.md b/_docs/promotions/promotion-flow.md
 #### Applications per defined environment
 To ensure a successful promotion, the product must include an application in each environment defined in the Promotion Flow.

 #### Application sync and health status
 Applications must be **Synced** and **Healthy** for a promotion to succeed.

 #### Multiple applications in a target environment
 If a target environment includes multiple applications for the same product—segmented for example by region, tenant, or other criteria—each application in that environment is updated with changes from the source environment.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -217,7 +217,7 @@ The table describes the possible deployment statuses for environments.
		{: .table .table-bordered .table-hover}
		\| Environment Status \| Description \|
		\|------------ \|---------------------------------------\|
		\| Successful \| Promotion to an environment is considered successful when the following conditions are met, in the order listed. {::nomarkdown}<ol><li>Pre-Action Workflow completed successfully.</li><li>Promotion Action submitted successfully. For PRs, the PR was successfully merged.</li><li>Application synced to the cluster.</li><li><li>Application is healthy.</li><li>Post-Action Workflow completed successfully.</li></ol>{:/}. \|
		\| Successful \| Promotion to an environment is considered successful when the following conditions are met, in the order listed. {::nomarkdown}<ol><li>Pre-Action Workflow completed successfully.</li><li>Promotion Action submitted successfully. For PRs, the PR was successfully merged.</li><li>Application synced to the cluster.</li><li>Application is healthy.</li><li>Post-Action Workflow completed successfully.</li></ol>{:/}. \|
		\| Running \| At least one step in a Pre- or Post-Action Workflow in the environment is currently in progress. \|
		\| Suspended \| One or both the Pre- and Post-Action Workflows or the Promotion Action is pending execution. This could be because of a condition in the Workflow or because a pull request is pending manual approval. \|
		\| Failed \| At least one step in a Workflow failed to execute, has a syntax error, was manually terminated, or the application is out of sync or degraded. \|
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -135,6 +135,9 @@ It is recommended to have a single application for a product in the Trigger Envi
		#### Applications per defined environment
		To ensure a successful promotion, the product must include an application in each environment defined in the Promotion Flow.

		#### Application sync and health status
		Applications must be Synced and Healthy for a promotion to succeed.

		#### Multiple applications in a target environment
		If a target environment includes multiple applications for the same product—segmented for example by region, tenant, or other criteria—each application in that environment is updated with changes from the source environment.

Expand Down