Merge pull request #312228 from xuehongg/xuehongg4

Recurrence trigger does not support waiting runs

Author: prmerger-automator[bot]

articles/logic-apps/logic-apps-limits-and-config.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: rohithah, laveeshb, rarayudu, azla
 ms.topic: reference
-ms.date: 02/07/2026
+ms.date: 02/24/2026
 ms.custom: sfi-image-nochange
 ---
 
@@ -175,7 +175,7 @@ The following table lists the values for an **Until** loop:
 | Name | Multitenant | Single-tenant | Notes |
 |------|-------------|---------------|-------|
 | Trigger - concurrent runs | Concurrency off: Unlimited <br><br>Concurrency on (irreversible): <br><br>- Default: 25 <br>- Min: 1 <br>- Max: 100 | Concurrency off: Unlimited <br><br>Concurrency on (irreversible): <br><br>- Default: 100 <br>- Min: 1 <br>- Max: 100 | The number of concurrent runs that a trigger can start at the same time, or in parallel. <br><br>**Note**: When concurrency is turned on, the debatching or **Split on** limit is reduced to 100 items for [debatching arrays](logic-apps-workflow-actions-triggers.md#split-on-debatch). <br><br>To change this value in multitenant Azure Logic Apps, see [Change trigger concurrency limit](logic-apps-workflow-actions-triggers.md#change-trigger-concurrency) or [Trigger instances sequentially](logic-apps-workflow-actions-triggers.md#sequential-trigger). <br><br>To change the default value in the single-tenant service, review [Edit host and app settings for logic apps in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md). |
-| Maximum waiting runs | Concurrency on: <br><br>- Min: 10 runs plus the number of concurrent runs <br>(Default)<br>- Max: 100 runs | Concurrency on: <br><br>- Min: 10 runs plus the number of concurrent runs <br>(Default)<br>- Max: 200 runs <br> | The number of workflow instances that can wait to run when your current workflow instance is already running the maximum concurrent instances. This setting takes effect only if concurrency is turned on. <br><br>To change this value in multitenant Azure Logic Apps, see [Change waiting runs limit](../logic-apps/logic-apps-workflow-actions-triggers.md#change-waiting-runs). <br><br>To change the default value in the single-tenant service, review [Edit host and app settings for logic apps in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md). |
+| Maximum waiting runs | Concurrency on: <br><br>- Min: 10 runs plus the number of concurrent runs <br>(Default)<br>- Max: 100 runs | Concurrency on: <br><br>- Min: 10 runs plus the number of concurrent runs <br>(Default)<br>- Max: 200 runs <br> | The number of workflow instances that can wait to run when your current workflow instance is already running the maximum concurrent instances. This setting takes effect only if concurrency is turned on. The **Recurrence** trigger doesn't support waiting runs and ignores any **Maximum waiting runs** value set on the trigger.  <br><br>To change this value in multitenant Azure Logic Apps, see [Change waiting runs limit](../logic-apps/logic-apps-workflow-actions-triggers.md#change-waiting-runs). <br><br>To change the default value in single-tenant Azure Logic Apps, see [Edit host and app settings for Standard workflows in single-tenant Azure Logic Apps](edit-app-settings-host-settings.md). |
 | Debatch or **Split on** items | Concurrency off: 100,000 items <br><br>Concurrency on: 100 items | Concurrency off: 100,000 items <br><br>Concurrency on: 100 items | For triggers that return arrays, you can specify an expression that uses the `splitOn` property, which [splits or debatches array items into multiple workflow instances](logic-apps-workflow-actions-triggers.md#split-on-debatch) for processing, rather than use a **For each** loop. This expression references the array to use for creating and running a workflow instance for each array item. <br><br>**Note**: When concurrency is turned on, the debatching or **Split on** limit is reduced to 100 items. |
 
 <a name="throughput-limits"></a>

articles/logic-apps/logic-apps-workflow-actions-triggers.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: reference
-ms.date: 07/17/2025
+ms.date: 02/24/2026
 ---
 
 # Schema reference guide for trigger and action types in Azure Logic Apps
@@ -461,8 +461,7 @@ This trigger runs based on the specified recurrence schedule and provides an eas
    },
    "runtimeConfiguration": {
       "concurrency": {
-         "runs": <max-runs>,
-         "maximumWaitingRuns": <max-runs-queue>
+         "runs": <max-runs>
       }
    },
    "operationOptions": "<operation-option>"
@@ -2524,6 +2523,10 @@ In the underlying trigger definition, add the `runtimeConfiguration.concurrency.
 }
 ```
 
+> [!NOTE]
+>
+> The **Recurrence** trigger supports concurrency but not waiting runs. The trigger ignores any value in the **Maximum waiting runs** parameter setting.
+
 For more information, see [Runtime configuration settings](#runtime-config-options).
 
 <a name="sequential-trigger"></a>