fix(Designer): Disable concurrency control settings for stateless workflows#9221
Conversation
Stateless workflows in Azure Logic Apps Standard do not support runtime configuration settings like concurrency control. When a user sets concurrency on a stateless workflow, the workflow fails to save. This change updates isConcurrencySupported() in both designer v1 and v2 to check the workflowKind and return false for stateless workflows, hiding the concurrency control toggle in the Settings panel. Fixes #9150 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
🤖 AI PR Validation ReportPR Review ResultsThank you for your submission! Here's detailed feedback on your PR title and body compliance:✅ PR Title
✅ Commit Type
✅ Risk Level
✅ What & Why
✅ Impact of Change
✅ Test Plan
✅ Contributors
✅ Screenshots/Videos
Summary Table
PR passes review. The advised risk level matches the submitter’s estimate and does not need to be raised.Last updated: Wed, 27 May 2026 16:21:13 GMT |
There was a problem hiding this comment.
Pull request overview
Disables concurrency control settings for stateless Standard Logic App workflows. Previously, enabling concurrency on a stateless workflow caused save failures; this change hides the concurrency toggle in the Settings panel by returning false from isConcurrencySupported when workflowKind === WorkflowKind.STATELESS. The fix follows the existing pattern already used for count and uploadChunk settings, which receive workflowKind through getOperationSettings.
Changes:
- Thread
workflowKindintoisConcurrencySupportedandgetConcurrency. - Return
falsefromisConcurrencySupportedfor stateless workflows. - Mirror the same change in both designer v1 and designer-v2.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| libs/designer/src/lib/core/actions/bjsworkflow/settings.ts | Pass workflowKind through to concurrency support/value helpers and short-circuit for stateless workflows. |
| libs/designer-v2/src/lib/core/actions/bjsworkflow/settings.ts | Same change applied to the v2 designer to keep behavior consistent. |
📊 Coverage CheckThe following changed files need attention:
Please add tests for the uncovered files before merging. |
Commit Type
Risk Level
What & Why
LA Standard stateless workflows do not support runtime configuration settings such as concurrency control. When a user enables concurrency control on a stateless workflow, the workflow fails to save with a backend error.
This change updates
isConcurrencySupported()in both designer v1 and v2 (libs/designer/andlibs/designer-v2/) to check theworkflowKindand returnfalsefor stateless workflows. This hides the concurrency control toggle in the Settings panel for stateless workflows, preventing the invalid configuration from being authored in the first place.The
workflowKindparameter was already being passed togetOperationSettings()and used for other settings (e.g.,count). This change follows the same established pattern to also gate concurrency support.Fixes #9150
Impact of Change
isConcurrencySupported()andgetConcurrency()now accept an optionalworkflowKindparameter. Existing callers withoutworkflowKindcontinue to work (parameter is optional).Test Plan
pnpm run build:libsucceeds for all libraries; Biome formatting and lint-staged hooks pass.Contributors
@rllyy97
Screenshots/Videos
N/A — toggle is hidden when workflow kind is
stateless.