Draft updates

Author: ecfan

articles/logic-apps/logic-apps-control-flow-loops.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: how-to
-ms.date: 08/18/2023
+ms.date: 09/13/2023
 ---
 
 # Create loops that repeat actions or process arrays in workflows with Azure Logic Apps
@@ -180,7 +180,7 @@ If you're working in code view, you can define the `For_each` action in your wor
 
 By default, the iterations in a **For each** loop run at the same time in parallel. However, when you have nested loops or variables inside the loops where you expect predictable results, you must run the those loops one at a time or sequentially.
 
-### [Consumption](#tab/standard)
+### [Consumption](#tab/consumption)
 
 1. In the **For each** action's upper right corner, select **ellipses** (**...**) > **Settings**.
 
@@ -239,7 +239,7 @@ In the following example workflow, starting at 8:00 AM each day, the **Until** a
 > This example uses Office 365 Outlook, but you can use [any email provider that Azure Logic Apps supports](/connectors/). 
 > If you use another email account, the general steps stay the same, but your UI might look slightly different.
 
-### [Consumption](#tab/standard)
+### [Consumption](#tab/consumption)
 
 1. In the [Azure portal](https://portal.azure.com), create a Consumption logic app resource with a blank workflow.
 
@@ -249,15 +249,15 @@ In the following example workflow, starting at 8:00 AM each day, the **Until** a
 
    | Property | Value |
    |----------|-------|
-   | **Interval** | 1 |
-   | **Frequency** | Day |
-   | **At these hours** | 8 |
+   | **Interval** | **1** |
+   | **Frequency** | **Day** |
+   | **At these hours** | **8** |
 
-   To add the **At these hours** parameter, open the **Add new parameter** list, and select **At these hours**, which is available only after you set **Frequency** to **Day**.
+   To add the **At these hours** parameter, open the **Add new parameter** list, and select **At these hours**, which appears only after you set **Frequency** to **Day**.
 
    ![Screenshot shows Azure portal, Consumption workflow designer, and Recurrence trigger parameters with selected option for At these hours.](./media/logic-apps-control-flow-loops/do-until-trigger-consumption.png)
 
-   When you're done, the trigger information box looks like the following example:
+   When you're done, the **Recurrence** trigger looks like the following example:
 
    ![Screenshot shows Azure portal, Consumption workflow, and Recurrence trigger parameters set up.](./media/logic-apps-control-flow-loops/do-until-trigger-complete-consumption.png)
 
@@ -267,9 +267,9 @@ In the following example workflow, starting at 8:00 AM each day, the **Until** a
 
    | Property | Value | Description |
    |----------|-------|-------------|
-   | **Name** | Limit | Your variable's name |
-   | **Type** | Integer | Your variable's data type |
-   | **Value** | 0 | Your variable's starting value |
+   | **Name** | **Limit** | Your variable's name |
+   | **Type** | **Integer** | Your variable's data type |
+   | **Value** | **0** | Your variable's starting value |
 
    ![Screenshot shows Azure portal, Consumption workflow, and parameters for built-in action named Initialize variable.](./media/logic-apps-control-flow-loops/do-until-loop-variable-properties-consumption.png)
 
@@ -281,7 +281,7 @@ In the following example workflow, starting at 8:00 AM each day, the **Until** a
 
    1. From the list, under **Variables**, select the variable named **Limit**.
 
-   1. From the middle operator list, select the **is equal** operator.
+   1. From the middle operator list, select the **is equal to** operator.
 
    1. In the rightmost box named **Choose a value**, enter **10** as the comparison value.
 
@@ -300,7 +300,7 @@ In the following example workflow, starting at 8:00 AM each day, the **Until** a
 
    ![Screenshot shows Consumption workflow and built-in action named Until with Name set to the Limit variable and Value set to 1.](./media/logic-apps-control-flow-loops/do-until-loop-increment-variable-consumption.png)
 
-1. Outside and under the loop, [follow these general steps to add an action that sends email](create-workflow-with-trigger-or-action.md?tabs=consumption#add-action).
+1. Outside and under **Until** action, [follow these general steps to add an action that sends email](create-workflow-with-trigger-or-action.md?tabs=consumption#add-action).
 
    This example continues with the **Office 365 Outlook** action named **Send an email**.
 
@@ -320,38 +320,119 @@ In the following example workflow, starting at 8:00 AM each day, the **Until** a
 
 ### [Standard](#tab/standard)
 
+1. In the [Azure portal](https://portal.azure.com), create a Standard logic app resource with a blank workflow.
+
+1. In the designer, [follow these general steps to add the **Recurrence** built-in trigger named **Schedule** to your workflow](create-workflow-with-trigger-or-action.md?tabs=standard#add-trigger).
+
+1. In the **Recurrence** trigger information pane, on the **Parameters** tab, specify the interval, frequency, and hour of the day for the trigger to fire.
+
+   The **At These Hours** parameter appears only after you set **Frequency** to **Day**.
+
+   | Property | Value |
+   |----------|-------|
+   | **Interval** | **1** |
+   | **Frequency** | **Day** |
+   | **At These Hours** | **8** |
+
+   When you're done, the **Recurrence** trigger information pane looks like the following example:
+
+   ![Screenshot shows Azure portal, Standard workflow, and Recurrence trigger parameters set up.](./media/logic-apps-control-flow-loops/do-until-trigger-standard.png)
+
+1. Under the trigger, [follow these general steps to add the **Variables** built-in action named **Initialize variable** to your workflow](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
+
+1. In the **Initialize variable** action information pane, on the **Parameters** tab, provide the following values:
+
+   | Property | Value | Description |
+   |----------|-------|-------------|
+   | **Name** | **Limit** | Your variable's name |
+   | **Type** | **Integer** | Your variable's data type |
+   | **Value** | **0** | Your variable's starting value |
+
+   ![Screenshot shows Azure portal, Standard workflow, and parameters for built-in action named Initialize variable.](./media/logic-apps-control-flow-loops/do-until-loop-variable-properties-standard.png)
+
+1. Under the **Initialize variable** action, [follow these general steps to add the **Control** built-in action named **Until** to your workflow](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
+
+1. In the **Until** action information pane, on the **Parameters** tab, provide the following values to set up the stop condition for the loop.
+
+   1. Under **Loop Until**, select inside the leftmost box named **Choose a value**, and select the option to open the dynamic content list (lightning icon).
+
+   1. From the list, under **Variables**, select the variable named **Limit**.
+
+   1. From the middle operator list, select the **is equal to** operator.
+
+   1. In the rightmost box named **Choose a value**, enter **10** as the comparison value.
+
+   ![Screenshot shows Standard workflow and built-in action named Until with finished stop condition.](./media/logic-apps-control-flow-loops/do-until-loop-settings-standard.png)
+
+1. Inside the **Until** action, select the plus (**+**) sign, and then select **Add an action**.
+
+1. [Follow these general steps to add the **Variables** built-in action named **Increment variable** to the **Until** action](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
+
+1. In the **Increment variable** action information pane, provide the following values to increment the **Limit** variable's value by 1:
+
+   | Property | Value |
+   |----------|-------|
+   | **Name** | Select the **Limit** variable. |
+   | **Value** | **1** |
+
+   ![Screenshot shows Standard workflow and built-in action named Until with Name set to the Limit variable and Value set to 1.](./media/logic-apps-control-flow-loops/do-until-loop-increment-variable-standard.png)
+
+1. Outside and under the **Until** action, [follow these general steps to add an action that sends email](create-workflow-with-trigger-or-action.md?tabs=standard#add-action).
+
+   This example continues with the **Office 365 Outlook** action named **Send an email**.
+
+1. In the email action information pane, on the **Parameters** tab, provide the following values:
+
+   | Property | Value | Description |
+   |----------|-------|-------------|
+   | **To** | <*email-address\@domain*> | The recipient's email address. For testing, use your own email address. | 
+   | **Subject** | **Current value for "Limit" variable is:** **Limit** | The email subject. For this example, make sure that you include the **Limit** variable to confirm that the current value meets your specified condition: <br><br>1. Select inside the **Subject** box so that the dynamic content list appears. <br><br>2. In the dynamic content list, next to the **Variables** section header, select **See more**. <br><br>3. Select **Lmiit**. |
+   | **Body** | <*email-content*> | The email message content that you want to send. For this example, enter whatever text you want. |
+
+   When you're done, your email action looks similar to the following example:
+
+   ![Screenshot shows Standard workflow and action named Send an email with property values.](./media/logic-apps-control-flow-loops/do-until-loop-send-email-standard.png)
+
+1. Save your workflow.
+
 ---
 
 ### Test your workflow
 
-1. To manually test your logic app, on the designer toolbar, select **Run Trigger** > **Run**.
+To manually test your logic app workflow, follow the steps based on whether you have a Consumption or Standard logic app.
 
+### [Consumption](#tab/consumption)
 
-After your workflow starts running, you get an email with the content that you specified:
+On the designer toolbar, select **Run Trigger** > **Run**.
 
-![Received email](./media/logic-apps-control-flow-loops/do-until-loop-sent-email.png)
+### [Standard](#tab/standard)
 
-<a name="prevent-endless-loops"></a>
+1. On the workflow menu, select **Overview**.
 
-## Prevent endless loops
+1. On the **Overview** page toolbar, select **Run** > **Run**.
 
-The "Until" loop stops execution based on these properties, so make sure that you set their values accordingly:
+---
 
-* **Count**: This value is the highest number of loops that run before the loop exits. For the default and maximum limits on the number of "Until" loops that a logic app run can have, see [Concurrency, looping, and debatching limits](../logic-apps/logic-apps-limits-and-config.md#looping-debatching-limits).
+After your workflow starts running, you get an email with the content that you specified:
+
+![Screenshot shows sample email received from example workflow.](./media/logic-apps-control-flow-loops/do-until-loop-sent-email.png)
+
+<a name="prevent-endless-loops"></a>
 
-* **Timeout**: This value is the most amount of time that the "Until" action, including all the loops, runs before exiting and is specified in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601). For the default and maximum limits on the **Timeout** value, see [Concurrency, looping, and debatching limits](../logic-apps/logic-apps-limits-and-config.md#looping-debatching-limits).
+### Prevent endless loops
 
-  The timeout value is evaluated for each loop cycle. If any action in the loop takes longer than the timeout limit, the current cycle doesn't stop. However, the next cycle doesn't start because the limit condition isn't met.
+The **Until** action stops execution based on the following properties, which you can view by selecting **Change limits** in the action. Make sure that you set these property values accordingly:
 
-To change these limits, in the loop action, select **Change limits**.
+| Property | Description |
+|----------|-------------|
+| **Count** | The maximum number of iterations that run before the loop exits. <br><br>For the default and maximum limits on the number of **Until** actions that a workflow can have, see [Concurrency, looping, and debatching limits](logic-apps-limits-and-config.md#looping-debatching-limits). |
+| **Timeout** | The maximum amount of time that the **Until** action, including all iterations, runs before the loop exits. This value is specified in [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601) and is evaluated for each iteration. <br><br>If any action in the loop takes longer than the timeout limit, the current iteration doesn't stop. However, the next iteration doesn't start because the timeout limit condition is met. <br><br>For the default and maximum limits on the **Timeout** value, see [Concurrency, looping, and debatching limits](../logic-apps/logic-apps-limits-and-config.md#looping-debatching-limits). |
 
 <a name="until-json"></a>
 
 ## "Until" definition (JSON)
 
-If you're working in code view for your logic app, 
-you can define an `Until` loop in your logic app's 
-JSON definition instead, for example:
+If you're working in code view, you can define an `Until` action in your workflow's JSON definition, for example:
 
 ``` json
 "actions": {
@@ -389,18 +470,14 @@ JSON definition instead, for example:
 }
 ```
 
-This example "Until" loop calls an HTTP endpoint, 
-which creates a resource. The loop stops when the 
-HTTP response body returns with `Completed` status. 
-To prevent endless loops, the loop also stops 
-if any of these conditions happen:
+This example **Until** loop calls an HTTP endpoint, which creates a resource. The loop stops when the 
+HTTP response body returns with `Completed` status. To prevent endless loops, the loop also stops 
+if any of the following conditions happen:
 
-* The loop ran 10 times as specified by the `count` attribute. 
-The default is 60 times. 
+* The loop ran 10 times as specified by the `count` attribute. The default is 60 times.
+
+* The loop ran for two hours as specified by the `timeout` attribute in ISO 8601 format. The default is one hour.
 
-* The loop ran for two hours as specified by the `timeout` attribute in ISO 8601 format. 
-The default is one hour.
-  
 ``` json
 "actions": {
    "myUntilLoopName": {
@@ -431,16 +508,9 @@ The default is one hour.
 }
 ```
 
-## Get support
-
-* For questions, visit the 
-[Microsoft Q&A question page for Azure Logic Apps](/answers/topics/azure-logic-apps.html).
-* To submit or vote on features and suggestions, 
-[Azure Logic Apps user feedback site](https://aka.ms/logicapps-wish).
-
 ## Next steps
 
-* [Run steps based on a condition (condition action)](../logic-apps/logic-apps-control-flow-conditional-statement.md)
-* [Run steps based on different values (switch action)](../logic-apps/logic-apps-control-flow-switch-statement.md)
-* [Run or merge parallel steps (branches)](../logic-apps/logic-apps-control-flow-branches.md)
-* [Run steps based on grouped action status (scopes)](../logic-apps/logic-apps-control-flow-run-steps-group-scopes.md)
+* [Run steps based on a condition (condition action)](logic-apps-control-flow-conditional-statement.md)
+* [Run steps based on different values (switch action)](logic-apps-control-flow-switch-statement.md)
+* [Run or merge parallel steps (branches)](logic-apps-control-flow-branches.md)
+* [Run steps based on grouped action status (scopes)](logic-apps-control-flow-run-steps-group-scopes.md)