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
We are trying to create a logic app in stateless mode, but would like to limit the concurrent runs due to limits in down stream backend systems.
The workflow uses service bus trigger(in built), when using designer mode it allows the concurrency limit to be turned on and enter the limit. But when I try to save the workflow, the validation fails with error runtime configurations are not available and switch to stateful mode. I could not find anywhere in documentations that concurrency is limited to stateful workflows. Even more confusing part is, it is allowed to be configured in designer mode in portal.
Could you please help me figure out if there is something that should be done to enable concurrent runs on stateless modes?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are trying to create a logic app in stateless mode, but would like to limit the concurrent runs due to limits in down stream backend systems.
The workflow uses service bus trigger(in built), when using designer mode it allows the concurrency limit to be turned on and enter the limit. But when I try to save the workflow, the validation fails with error runtime configurations are not available and switch to stateful mode. I could not find anywhere in documentations that concurrency is limited to stateful workflows. Even more confusing part is, it is allowed to be configured in designer mode in portal.
Could you please help me figure out if there is something that should be done to enable concurrent runs on stateless modes?
Beta Was this translation helpful? Give feedback.
All reactions