rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Stopped flows

Last updated Policies Sprawl & Lifecycle Power Automate

AI summary

Rencore Governance identifies Power Automate flows that have stopped, either because Power Automate disabled them automatically after errors or inactivity, or because owners turned them off and forgot. Check with owners whether each stopped flow is still needed, then turn it back on or delete it.

Severity: High Sprawl Recommended Generally available

What it detects

Shows Flows that have stopped.

Why it matters

A stopped flow does not run at all. Power Automate turns flows off by itself after 14 days of continuous errors and, for some licenses, after 90 days without a trigger, and owners sometimes turn a flow off and forget it. Check with the owners whether each flow is still needed, then turn it back on or delete it.

The rule

Every Flow where State equals 'Stopped'

In Rencore Governance

The Stopped flows policy in Rencore Governance: the rule, its trend and the objects that match it
The policy page in a Rencore demo Environment, captured October 2026.

Details

Applies to Flow
Connector Power Automate
Severity High
Category Sprawl
Recommended Yes
Recommended automation None
License type Standard

Other policies that check Flow objects:

Frequently asked questions

What does the stopped flows policy detect?

The Stopped flows policy shows Flows that have stopped.

Which objects does the stopped flows policy check?

The Stopped flows policy checks Flow objects from the Power Automate inventory and reports each one that matches its rule as a violation.

How severe is a violation of the stopped flows policy?

Violations of the Stopped flows policy have High severity. The policy is in the Sprawl category.

Which module includes the stopped flows policy?

The Stopped flows policy comes with the Power Automate connector in the Apps, Automation & BI module of Rencore Governance, an add-on module on the Premium and Enterprise Plans.