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 attempting to revert a workflow and turn off a previously configured trigger concurrency limit.

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

Workflow 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 attempting to remove the concurrency configuration, 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 limits are treated as runtime configuration.

Once configured:

The setting becomes immutable
It cannot be turned off
Reverting the workflow to a version without the limit is blocked
Editing or changing the trigger may also become restricted

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.

What you can do instead (Logic Apps Standard)

Because the concurrency limit cannot be removed from an existing workflow, the practical options are:

Option A — Create a new Logic App workflow (only way to remove the limit)

Clone or copy the Logic App workflow file (manually via SCM/Kudu or from source control)
Create a new folder and then create workflow.json file without the concurrency configuration
Disable the original Logic App workflow

This results in a clean workflow where:

The trigger can be changed
No concurrency limit exists

⚠️ This creates a new Logic App with new run history.

Option B — Keep the Logic App and neutralize the limit

If the goal is to reduce throttling rather than remove concurrency control:

Increase the concurrency runs value (for example, to 100)

This does not remove concurrency control and the trigger still cannot be changed, but it reduces the practical impact of the limit.

Key takeaway

In Logic Apps Standard, a trigger concurrency limit cannot be removed once configured
Reverting or turning off the limit in the Azure portal is not supported
Removing the limit requires a new Logic App
Increasing the limit is the only way to keep the existing Logic App running