You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run waiting option needs to set maximumWaitingRuns parameter.
However there is limitation run waiting option wouldn't work anyway even if user add runtimeConfiguration.concurrency.maximumWaitingRuns later, after user save workflow has only runtimeConfiguration.concurrency.runs parameter without setting runtimeConfiguration.concurrency.maximumWaitingRuns parameter.
Especially, if user set trigger concurrency in Logic Apps designer's GUI, in current design workflow automatically will be saved workflow has only runtimeConfiguration.concurrency.runs parameter.
In such situation, user never enable run waiting option to that workflow.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 4a0dd3aa-82c2-4510-1413-a109eddf6303
Version Independent ID: 21f0f699-9267-821f-07aa-998f7dfc32f2
Run waiting option needs to set maximumWaitingRuns parameter.
However there is limitation run waiting option wouldn't work anyway even if user add runtimeConfiguration.concurrency.maximumWaitingRuns later, after user save workflow has only runtimeConfiguration.concurrency.runs parameter without setting runtimeConfiguration.concurrency.maximumWaitingRuns parameter.
Especially, if user set trigger concurrency in Logic Apps designer's GUI, in current design workflow automatically will be saved workflow has only runtimeConfiguration.concurrency.runs parameter.
In such situation, user never enable run waiting option to that workflow.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: