Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Automate - Using Flows
Unanswered

Flow: Your operation has been throttled

(1) ShareShare
ReportReport
Posted on by 2

Hello, everyone!

 

I'm new at Power Automate and I am having some issues with a flow I created.

It's a simple flow that refreshes the Power Bi dataset as soon as a file in a Sharepoint folder is updated.

It was working OK, but it stopped working this week. It seems that the trigger is working, since I can see a message that it's running and then it fails and I receive a e-mail saying that my operation has been throttled.

 

Did anyone have similar problems with a flow that simple?

 

Thanks!

 

cfkc_0-1638542122253.pngcfkc_1-1638542142716.png

cfkc_2-1638542163174.png

 

  • lsener Profile Picture
    2 on at
    Re: Flow: Your operation has been throttled

    @cfkc . Did you ever find a reason this happened? I too am experiencing this exact same thing. Mine is set to trigger when a file is updated in Sharepoint (I tried a few variations. This screen shot is from testing the trigger "When an item or a file is modified" rather than using the one for when a folder is modified, then refresh a dataset). The first few times it worked just fine, but then stopped and I got the throttled warning. I'm guessing part of this was that the Autosave function was saving too many times and triggering concurrently, so I turned this off to only manually save 1 time. Even in testing though it still doesn't seem to be working. 

     

    I also thought having this run through a synced folder one my OneDrive, rather than connecting directly through to the Sharepoint site, might be the culprit so I tested with both ways. (You'll see this referenced in the Dataset name)

     

    lsener_0-1648214219750.png

     

  • ScottShearer Profile Picture
    25,218 Most Valuable Professional on at
    Re: Flow: Your operation has been throttled

    @cfkc 

    Here is a link to documentation that may provide some insight.  

    It is likely that this Flow (or another Flow you have created) is running an excessive number of times or is otherwise consuming resources in excess of stated limits.

    I see that the trigger is on a library - when someone is editing a document many saves can occur causing the Flow to run for each one.  You might change your Flow to one that runs periodically (once an hour?) and finds documents that have been updated in the last hour and then refreshes the dataset.

     

     

     

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Understanding Microsoft Agents - Introductory Session

Confused about how agents work across the Microsoft ecosystem? Register today!

Markus Franz – Community Spotlight

We are honored to recognize Markus Franz as our April 2025 Community…

Kudos to the March Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 146,702 Most Valuable Professional

#2
RandyHayes Profile Picture

RandyHayes 76,287 Super User 2024 Season 1

#3
Pstork1 Profile Picture

Pstork1 66,026 Most Valuable Professional

Leaderboard

Featured topics

Restore a deleted flow