Logic apps skipping triggers

Question

I've a logical app that triggers when a new email arrives on Gmail inbox with attachment in it. Although we're having emails in our inbox that has attachment in it yet logical app is skipping those triggers.
This issue is very regular and its not limited to 10-15 skip. It is skipping more than 100 emails. When we forward these emails again to same inbox then logical app works fine.

FYI

• our logical app is running on consumption plan

Answer 1

@HIMANSHU MITTAL Thanks for reaching out. Here are some known issues and limitations with Gmail connector.

• The When a new email arrives trigger may skip emails if you are receiving more than 300 emails per 30 seconds interval. Consider configuring your flow with additional filter parameters to reduce number of emails.
• The When a new email arrives trigger may intermittently skip emails with attachments if you are using a Google Workspace (formerly G Suite) account. This happens because in some case Gmail API takes a long time to process emails (possibly due to security scans of attachments), so the emails are received with a certain delay.

As possible workaround please try the following:

• Use tiny emails (without attachments), try to send them not so frequently.
• Use another consumer Gmail account and configure auto-forwarding from the Google Workspace account to this new consumer Gmail account. Configure the trigger against this new account. Since this is a consumer account, we believe that the delay will be minimized and the trigger will not skip such emails.
• Use a custom connector to ListMessage API with a q parameter:
  • Create an action to list messages for the last 5 minutes. You can do so using q parameter. Example of q param value - after:1649457986. You should provide current time - 5min epoch time as the action input.
  • • 1649457986 is the epoch time that represents "Friday, April 8, 2022 3:46:26 PM GMT-07:00".
  • Check nextPageToken value from the response until it is empty. If it is not empty then you need to call the same API with pageToken parameter value set to the nextPageToken from the response. You can do so using "Until" loop for example.
  • Filter out those messages IDs which have already been processed in previous runs (e.g. you can use Azure Table Storage connector to store already processed IDs)
  • Use Get email details action to get email content by ID