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

Source: Dev.to

Problem Overview

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

• The trigger concurrency limit is set in the workflow.
• The workflow runs successfully.
• Attempting to remove the concurrency configuration during a revert causes the Save or Publish action to fail.

Error example

Trigger concurrency runtime configuration cannot be removed

Why This Happens

In Logic Apps Standard, trigger concurrency is treated as a runtime configuration. Once it is enabled:

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

This is expected platform behavior.

Impact

• Deleting and recreating the Logic App workflow without the concurrency limit would solve the issue, but it also deletes the entire run history, breaking operational and audit continuity.
• In many production environments, losing run history is not acceptable.

Workaround: Edit the Deployed workflow.json

You can align the deployed workflow with Azure’s locked runtime configuration without deleting the Logic App or losing its run history.

Steps

1. Open the Logic App in the Azure portal
   Azure Portal → Logic App Standard

2. Launch Advanced Tools (Kudu)

   • Click Advanced Tools → Go.

3. Open the Debug Console

   • Choose PowerShell or CMD.

4. Navigate to the workflow file

   site/wwwroot/.../workflow.json

5. Remove the trigger concurrency configuration
   Locate the runtimeConfiguration section and delete the concurrency block, e.g.:

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

   After removal, the section should be either omitted entirely or left empty.

6. Save the file.

7. Restart the Logic App (if required) to apply the changes.

Visual Aid

The following GIF demonstrates editing the workflow using the Kudu console:
(Insert GIF or screenshot here)

Summary

• Trigger concurrency cannot be turned off once enabled via the portal.
• Reverting a workflow that removes concurrency will fail.
• Editing the deployed workflow.json directly removes the runtime configuration, allowing the revert to succeed while preserving the original run history.

References

• Sandro Pereira’s detailed post on the platform limitation.