Skip to main content

Notifications

Power Automate - Using Connectors
Answered

API requests limit when using Google Sheets connector

(0) ShareShare
ReportReport
Posted on by 103

I'm struggling to find a solution for reading a few hundred rows from four shared Google Sheets. During the flow development, I encounter rate limit errors after a few minutes of work ("Too many requests sent to the Google Sheets API."). Additionally, when I initiate the flow, I quickly hit the rate limit as well.

 

Has anyone encountered similar issues with this connector? Specifically, any experience with managing the rate limit? Is there an option to pay Google to increase the limit (from the Power Automate connector)?

 

Thank you for your assistance!

 

Best regards,

Elowy

  • Elowy GrootCRM Profile Picture
    Elowy GrootCRM 103 on at
    Re: API requests limit when using Google Sheets connector

    Appreciate it, Gill!

     

    I did come across these limits eventually, but it seems they are (somehow) even more restrictive. Perhaps there are more requests per action under the hood. Even when I make an update call every 2 seconds, it still hits the limits, and, somehow, it gets blocked for several minutes.

     

    I've also incorporated the retry time. However, most of the time you have to endure a prolonged wait before the flow becomes successful.

     

    Once again, thank you for your response!

  • Verified answer
    Gdarmon Outlook Profile Picture
    Gdarmon Outlook 372 on at
    Re: API requests limit when using Google Sheets connector

    According to Google’s documentation, the Google Sheets API has per-minute quotas that are refilled every minute. For example, there’s a read request limit of 300 per minute per project. If your app sends 350 requests in one minute, the additional 50 requests exceed the quota and generates a 429: Too many requests HTTP status code response.

    To manage the rate limit, you can try using an exponential backoff algorithm to retry requests that fail due to rate limiting. An exponential backoff algorithm retries requests using exponentially increasing wait times between requests, up to a maximum backoff time. If requests are still unsuccessful, it’s important that the delays between requests increase over time until the request is successful.

     

    Gill

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

Microsoft Kickstarter Events…

Register for Microsoft Kickstarter Events…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Announcing Forum Attachment Improvements!

We're excited to announce that attachments for replies in forums and improved…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 145,475

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,767

Leaderboard

Featured topics