Skip to main content

Notifications

Power Automate - Using Connectors
Unanswered

Gmail connector issue

(0) ShareShare
ReportReport
Posted on by 169

Hi all,

 

We've been using gmail connector as a trigger to many flows ("When a new email is received") and we've noticed that, when the gmail connection hits a limit (for example, when an email has an attachment > 35MB or when there is a rate limit) the gmail connection probably tries to receive the same email for days - without sending any notification to us about the problem - and after two or three weeks the flow activity is suspended and we get a notification from power automate. So, for about 2-3 weeks, the flow is inactive and we have not figured out a way to promptly notice this and manage it.

 

The flow is off, there is no way of turning it on because there is the warning "there is an issue with the trigger in this flow" and inside the flow there is the message "Response content length exceeds maximum value 35 MB" or a similar rate limit error.

 

In this case, we copy the flow using the same gmail connection and the copied flow works.

 

We absolutely need a way to handle this better, to get notified sooner that the gmail connection has hit a limit. Any suggestion would be much appreciated.

  • fmigacz Profile Picture
    fmigacz on at
    Re: Gmail connector issue

    I think you're going to need a custom connector, or just some HTTP connectors. We also recommend this for large attachments when the security scanning process delays until the connector's request times out. In our example, Gmail - Connectors | Microsoft Docs, we build a custom connector to call the Google API with a query parameter. This query parameter can use any of the Google Gmail search syntax strings. In your case, you can add size:35MB or a similar value to the API request.

    Here is Google's documentation: 

    https://developers.google.com/gmail/api/reference/rest/v1/users.messages/list#query-parameters 

     

    It doesn't give examples of error responses, but you can play around with it to find out when your request is unsuccessful due to large file scanning delays and when your request is unsuccessful due to throttling (HTTP 429?).

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,691

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 65,019

Leaderboard

Featured topics