Gmail Trigger node polls repeatedly for multiple times for same email even though the workflow is successful

[Mahesh_Thiru]

Gmail Trigger node runs repeatedly for the same email multiple times Despite of workflow being successful.

No error message

Please share your workflow

Information on your n8n setup

• n8n version: 0.218.0
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main): default
• Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
• Operating system: Linux

[Mahesh_Thiru]

This is with reference to the below issue

Gmail node getting triggered multiple times for same email

Hey Team, I am using the Gmail Trigger node as a trigger for my workflow. I have set the poll time for the node to every minute. There have been multiple instances where the Gmail node triggers the same workflow multiple times. Is this a bug in N8N, or do I need to update some configuration in the Gmail node? No error message Please share the workflow Note - I have removed client id and client secret from the Gmail Node. Information on your n8n setup [email protected] - R…

As per the last comment from Jon, This issue happens for selective emails. And I can see a pattern in them. But still I am not sure if this is the cause.

I can see that this issue happens for mails when the label “UNREAD” is not in the list of labels in the json inside Gmail trigger node. I can observe this for 10 instances from the morning.

However I am not sure why a new email will not have a UNREAD tag. May be a bug from gmail api or downtime during the poll.

I believe “Unread” label must be applied by default for all the poll in n8n. Please let me know your thoughts. If you do not include Labels filter in the Gmail trigger node and send email to the connected gmail account continuously, say 1 email per minute to test, this issue can be reproduced.

[EmeraldHerald]

Hi @Mahesh_Thiru I had a quick look and this is a known bug at the moment with the Gmail trigger - I’ll let you know when I have any updates this one.

A workaround could be to use the schedule trigger to fetch unread emails every so many minutes and mark them as read, and that would avoid the issue

[Mahesh_Thiru]

Hi @EmeraldHerald
Thank you for the response. I am doing that now. Just sharing this in the community, so that this can be a possible input for the dev team based on the last response for question # 23568. Thank you again for the workaround provided.

Regards.
Mahesh

[jan]

New version [email protected] got released which includes the GitHub PR 9424.