Merge pull request #281345 from EldertGrootenboer/capacity-efforts

prmerger-automator[bot] · web-flow · commit 39a812c840b4 · 2024-07-19T20:43:34.000Z
Added note that capacity fulfilment is done to the best of our effort.
diff --git a/articles/service-bus-messaging/automate-update-messaging-units.md b/articles/service-bus-messaging/automate-update-messaging-units.md
@@ -143,7 +143,7 @@ The previous section shows you how to add a default condition for the autoscale
     > [!NOTE]
     > - The metrics you review to make decisions on autoscaling may be 5-10 minutes old. When you are dealing with spiky workloads, we recommend that you have shorter durations for scaling up and longer durations for scaling down (> 10 minutes) to ensure that there are enough messaging units to process spiky workloads. 
     > 
-    > - If you see failures due to lack of capacity (no messaging units available), raise a support ticket with us.  
+    > - If you see failures due to lack of capacity (no messaging units available), raise a support ticket with us. Capacity fulfillment is subject to the constraints of the environment and is carried out to our best effort.
 
 ## Run history
 Switch to the **Run history** tab on the **Scale** page to see a chart that plots number of messaging units as observed by the autoscale engine. If the chart is empty, it means either autoscale wasn't configured or configured but disabled, or is in a cool down period.  

Original file line number	Diff line number	Diff line change
`@@ -143,7 +143,7 @@ The previous section shows you how to add a default condition for the autoscale`
`143`	`143`	`> [!NOTE]`
`144`	`144`	`> - The metrics you review to make decisions on autoscaling may be 5-10 minutes old. When you are dealing with spiky workloads, we recommend that you have shorter durations for scaling up and longer durations for scaling down (> 10 minutes) to ensure that there are enough messaging units to process spiky workloads.`
`145`	`145`	`>`
`146`		`- > - If you see failures due to lack of capacity (no messaging units available), raise a support ticket with us.`
	`146`	`+ > - If you see failures due to lack of capacity (no messaging units available), raise a support ticket with us. Capacity fulfillment is subject to the constraints of the environment and is carried out to our best effort.`
`147`	`147`
`148`	`148`	`## Run history`
`149`	`149`	`Switch to the Run history tab on the Scale page to see a chart that plots number of messaging units as observed by the autoscale engine. If the chart is empty, it means either autoscale wasn't configured or configured but disabled, or is in a cool down period.`