n8n - 💡(How to fix) Fix Gmail Search node executes again after workflow successfully finishes [1 comments, 2 participants]

Bug Description

The Gmail - Search Messages node gets executed again after the workflow has already continued successfully through later nodes.

<img width="1380" height="840" alt="Image" src="https://github.com/user-attachments/assets/3f3bb32f-8e9b-432a-87c6-6d32118b3afe" />

There is no loop in the workflow and no connection leading back to the Gmail node.

Even after removing the final notification nodes, the Gmail node still re-executes by itself.

I also tried enabling Execute Once in the Gmail node settings, but it did not help.

<img width="1205" height="669" alt="Image" src="https://github.com/user-attachments/assets/0b168ba1-d045-4b39-a4fc-21ba397ec9a9" />

To Reproduce

1. Run workflow manually or via schedule trigger
2. Workflow executes normally
3. After later nodes finish, Gmail - Search Messages executes again unexpectedly
4. Workflow may continue re-triggering from that node

Expected behavior

The Gmail node should execute only once during the workflow execution unless explicitly connected in a loop.

Debug Info

n8n version: 2.18.5 - Deployment: Self-hosted Docker Database: PostgreSQL Execution mode: Task runners enabled

Workflow attached:

Previous Month Invoices → ZIP → Drive.json

Operating System

Debian GNU/Linux 13

n8n Version

2.19.5

Node.js Version

docker

Database

PostgreSQL

Execution mode

main (default)

Hosting

self hosted