Unanswered

Outlook Connector Lag

(1) Share

Report

Posted on by CU03101624-0

I have a SharePoint‑triggered flow: users upload a folder of files, set the custom column ReadyToFax = true, and the flow starts. It loops through each file, gets its content, emails it from a shared inbox to a fax service, then marks the file’s Faxed column as true or false depending on the result. A delay is included in the loop to limit API calls and avoid overloading the fax service.

The flow works for a while, then suddenly stalls—runs for days without errors, never completes, and never sends more emails. I’ve already set concurrency to 1, removed retries, reduced library items, and ensured only one flow runs at a time. Analytics shows many 429 and Bad Request errors from “Send an email (V2)” and even a trigger gateway timeout. I’ve tried both email actions with the same result.

Could this be caused by hitting Power Automate limits with only a standard M365 license? Oddly, a manual‑triggered copy of the same flow always finishes successfully, even though it also shows some 429s.

Thanks—I'm self‑taught and running out of ideas.

Old/New designer screenshots below:

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

Sort by

David_MA 14,956 Super User 2026 Season 1 on at

Like
a
(2)

Report
Copy link

Link copied!

It looks like your flow is getting stuck in a loop. The trigger is When a file is modified, and inside the flow you update the file’s properties. That update counts as another modification, so it triggers another run of the flow.

On top of that, every time the flow triggers, you run a Get files that returns all items where ReadyToFax is true. That means each run re‑processes every ready file, not just the one that changed. With multiple runs piling up, the flow eventually gets overwhelmed and stalls.

A simpler pattern would be to trigger only when a file is created, not modified. Then process only that single file. Update the faxed column, which will not retrigger the flow since it only runs when the file is created.

To handle the failed runs, use a separate scheduled flow that runs hourly and picks up only the files where ReadyToFax is true and Faxed is false so you can retry them safely.

Was this reply helpful? Yes No
CU03101624-0 29 on at

Like
a
(0)

Report
Copy link

Link copied!

There are trigger conditions on the trigger to prevent infinite regression. Only items with {IsFolder} = true, ReadyToFax = true, Faxed = false trigger the flow @David_MA

I'm also only getting the files within the folder marked ReadyToFax (which is itself only indicated at the folder level, not the files within it). triggerBody()?['{FilenameWithExtension}'] is going directly into the "Limit entries to folder" parameter in the "Get file (properties only)" action

Was this reply helpful? Yes No