Logic App Standard: Cannot Turn Off Trigger Concurrency After It Was Enabled

#logicapps #azure #kuduconsole #lowcode

When working with Azure Logic Apps Standard, you may run into an issue when reverting a workflow and trying to turn off the trigger concurrency limit.

In Logic Apps Standard, trigger concurrency limits cannot be removed once configured — reverting the change in the Azure portal is not possible.

Workflow revert scenario

A typical scenario looks like this:

A trigger concurrency limit is configured
The workflow runs successfully
Below is the workflow HTTP trigger with the concurrency limit enabled. This is an asynchronous logic app.

Error when turning off concurrency

When removing the concurrency configuration during a revert, the save or publish action fails with an error:

Error message (or similar):

Trigger concurrency runtime configuration cannot be removed

Why this happens

In Logic Apps Standard, trigger concurrency is treated as a runtime configuration.

Once enabled:

It becomes immutable
It cannot be turned off
Reverting to a workflow version without concurrency is blocked

This is expected platform behavior.

Why recreating the Logic App is not ideal

Deleting and recreating the Logic App workflow without the concurrency limit would technically solve the issue, but it would also:

Delete the entire run history
Break operational and audit continuity

In many production environments, this is not acceptable.

Workaround that keeps run history (Logic Apps Standard)

To revert the workflow without deleting the Logic App and without losing run history, you can align the deployed workflow with Azure’s locked runtime configuration.

Steps

Go to Azure Portal → Logic App Standard
Open Advanced Tools (Kudu)
Open the Debug Console
Navigate to the deployed workflow file:

   site/wwwroot/.../workflow.json

Remove the trigger concurrency configuration:

"runtimeConfiguration": {
  "concurrency": {
    "runs": 5
  }
}

Save the file
Restart the Logic App if required

The following GIF shows editing the workflow using the Kudu console:

⚠️ This workaround turns off the concurrency limit that was previously configured via the Azure portal, while preserving the original run history.

Key takeaway

In Logic Apps Standard, trigger concurrency cannot be turned off once enabled
Reverting a workflow that removes concurrency will fail in portal.
Editing the deployed workflow.json via kudu allows the revert to succeed.
Original run history is retained