Logic app workflow got disabled automatically

### Severity

P1 - Critical (Blocking production)

### Describe the Bug with repro steps

The Logic App workflow should remain enabled and continue triggering according to the configured recurrence schedule unless it is explicitly disabled by a user or deployment.

Actual behavior
The Logic App workflow was found in a disabled state without any manual intervention from our team. As a result, the scheduled execution stopped running automatically and required manual re-enablement.

Context
The workflow is configured with a Recurrence trigger that runs on a daily schedule and invokes an Azure Function via HTTP POST. The workflow had previously been running successfully and processing scheduled executions as expected.

During investigation:

No team member intentionally disabled the workflow.

The workflow state was discovered as Disabled in the Azure portal.

This caused the scheduled process to stop executing until manually re-enabled.

Steps to reproduce

Create a Logic App with a Recurrence trigger.

Configure the workflow to call an Azure Function.

Allow the workflow to run on schedule for multiple executions.

At some point the workflow appears in a Disabled state without explicit action.

Impact
This causes production scheduled processes to stop executing silently, which can delay downstream integrations until the workflow is manually re-enabled.

Severity
P1 – Critical (Blocking production automation)

### What type of Logic App Is this happening in?

Consumption (Portal)

### Are you experiencing a regression?

The workflow had been running successfully on a daily recurrence schedule prior to this incident. We discovered it in a disabled state on March 5, 2026 without any manual change from our team. The last known working executions occurred before the workflow was automatically disabled.

### Which operating system are you using?

Windows

### Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

### Workflow JSON

```json
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"actions": {
"Call_an_Azure_function": {
"type": "Function",
"inputs": {
"method": "POST",
"body": [
{
"ClientCode": "CYCOLOGY"
}
],
"function": {
"connectionName": "azureFunctionOperation-15"
}
},
"runAfter": {}
}
},
"contentVersion": "1.0.0.0",
"outputs": {},
"triggers": {
"Recurrence": {
"type": "Recurrence",
"recurrence": {
"interval": 1,
"frequency": "Day",
"timeZone": "Pacific Standard Time",
"schedule": {
"hours": [
3
],
"minutes": [
0
]
}
}
}
}
},
"kind": "Stateful"
}
```

### Screenshots or Videos

_No response_

### Environment

Browser: Google Chrome (latest version)
Operating System: Windows 11
Logic App Type: Consumption (Portal)
Azure Region: [your region – e.g., Canada Central / West US]
Deployment Method: Azure Portal
Azure CLI: Not used for this workflow

The workflow is a Logic App with a Recurrence trigger that runs daily and invokes an Azure Function via HTTP POST.

### Additional context

_No response_

No repository file or test is named. Start with the supplied workflow JSON and the Azure portal for a Consumption Logic App, checking the workflow state and execution history around the March 5, 2026 disablement. Done means identifying a reproducible cause or missing evidence for the automatic disablement and documenting the conditions that prevent scheduled executions from stopping silently.

Written by the indexing model from the issue text.