Many flows have stopped functioning as intended for inconsistent reasons

(0) Share

Report

Posted on by SQ-23062143-0

Hi all,

I have had over the last 2 weeks or so multiple flows, that were previously running completely fine just stop running fine.

Some getting Graph connection errors, that disappear on a re-run of the flow.

One not pulling all the information out of a powerapp that's connected to it. Though it may be an issue with the powerapp.

One that has a trigger that just stopped working, for no discernable reason. It's a "When a file is added to a folder" trigger.

Is this a general service degradation? Is there an issue with our environment? What could be the cause. It's all very confusing.

Insight and solutions would be appreciated.

Thanks

Sam

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @SQ-23062143-0,

What you're describing is something many teams experience, and it’s usually not a single root cause.

Based on the symptoms:

Graph errors that resolve on re-run are typically transient (API throttling, token refresh, backend instability)

File triggers not firing is a known limitation, especially with moves, sync operations, or connection issues

Power Apps not passing full data could point to payload or schema inconsistencies rather than platform degradation

In most cases, this combination points to:

Expired or unstable connections

Connector/API intermittency (Graph, SharePoint, etc.)

Trigger limitations or missed events

Possible environment or policy changes

Recommended actions:

Re-authenticate all connectors

Add retry policies to critical actions

Implement error handling (Try/Catch using scopes)

Avoid relying solely on file-based triggers for critical processes (consider scheduled checks)

Review run history patterns to identify if failures are transient or systemic

If failures resolve on resubmit, it’s almost always a transient platform/connector issue rather than a flow design issue.

✅ If one of the responses here solved your issue, please mark it as Accepted so others facing the same problem can benefit as well.
👍 If this or any other reply here helped you, feel free to give it a Like. It helps others and is always appreciated.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/

Was this reply helpful? Yes No
Suggested answer

MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@SQ-23062143-0,

Powerapps -> Navigate to Connections and check is there any connection is broken.

If its broken reconnect with all the broken connections.

Power Apps connections typically break or ask you to reconnect due to expired authentication tokens, password resets, multi-account caching issues, or inactivity timeouts. Additionally, Data Loss Prevention (DLP) policies set by your organization can automatically disable connectors.

For More Information : https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/connections/troubleshoot-broken-connections

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Do you have a Power Automate Premium license. If not, I would suggest upgrading to that as it has higher limits and with it flows will not get deactivated from lack of use. If you do not already do this, create your workflows in solutions. This explains benefits of using solutions: Understand the benefits of using solution-aware cloud flows - Power Automate | Microsoft Learn.

In addition to what the others said, I would add that it's difficult to determine whether these issues are related to a platform problem or individual flow design/configuration without more details. The examples you provided involve several different components of the Power Platform, and each could have different root causes. Some intermittent issues can be caused by connector behavior, while others may stem from design decisions, trigger configuration, error handling, or connection management within the flows themselves. If you can share specific error messages, screenshots, or details about how the affected flows are configured, the community will be in a much better position to help identify the root cause.

Was this reply helpful? Yes No