LogicApps workflows not triggering

Hi @Kurt Carvalho

Thank you for reaching out to Microsoft Q&A.

Can you please fill the form I have shared in the Private chat?

Meanwhile, can you check the points below:

The issue you are facing is related to Azure Logic Apps (Standard) runtime entering a degraded state due to sustained high memory pressure. When the Logic App backend restarts multiple times because of memory exhaustion, the runtime may stop triggering workflows altogether. In this state, restarting the workflow or even upgrading the plan (for example, to WS3 Standard) does not automatically recover the runtime. This happens because the upgrade only increases available resources, but it does not reset or clean up the unhealthy runtime state or address the workflow design patterns that originally caused the memory pressure. As a result, triggers may not fire and no workflow runs are created even after scaling up.

Refer below points to resolve this issue or as a workaround:

1. Restart the Logic App Standard app (App Service level) Restart the entire Logic App Standard application (not just the workflow). This forces the worker process to recycle, and releases memory held by the runtime. A workflow-only restart is usually insufficient in high-memory-pressure scenarios.

2. Disable memory‑heavy workflows temporarily Identify and disable workflows that process large payloads, run large loops, or use built‑in connectors that load full data into memory. Disabling these workflows allows the runtime to stabilize before re‑enabling them.

3. Scale out, not only scale up Ensure the Logic App is running on more than one instance. Scaling out reduces the chance of a single worker becoming memory-starved and blocking all triggers.

4. Optimize workflow design to reduce memory usage Refactor workflows to avoid loading large payloads into memory. Use pagination, chunked processing, asynchronous patterns, and stateless workflows where possible to minimize memory pressure.

5. Enable diagnostics and monitor memory usage Enable Application Insights or Log Analytics and review memory, CPU, and action execution duration. This helps identify which workflow or action caused the memory spike leading to backend restarts.