Duplicate Emails Sent with Different Content — Only One Execution in Logs

A while ago, I built a workflow that reads a set of emails and generates a summary of the most important ones — everything was working fine.

However, about three days ago I noticed that two emails are being sent every time, but with different content.

Here’s the setup: I have a workflow that runs every 30 minutes and generates a summary email.
When I check the execution logs, I can confirm there’s only one execution every 30 minutes, and the output is just one item with a single HTML summary.

For some strange reason, I’m receiving two separate emails, not duplicates — their content is similar but not the same. What’s weird is that n8n only shows one execution, yet two different emails are sent out.

**I’m attaching screenshots and logs as evidence.

Last execution**

Items sent in last execution (1 item only): I’ve been testing using the “pruebas 2” node, but as you can see, the node is deactivated — so it can’t be the reason why I’m receiving 2 emails instead of 1.
Even if the deactivation somehow failed, the email content should be exactly the same, not different.

Received output:

Content from email received at 6:30 AM:

Content from email received at 6:31 AM:

Email sent by n8n workflow: which corresponds to the email received at 6:31 AM

Content in both mails are different (but the main context is the same).

Any ideas why my workflow is generating double mails but only shows one execution with one item?

Based on the issue and similar reports ([github.com]( Duplicate Outlook Emails · Issue #19602 · n8n-io/n8n · GitHub ), [community.n8n.io]( Gmail triggered multiple times for same email )), here’s what to check:

1. **Verify node connections**: Ensure only one email node is active and receiving data.

2. **Check for workflow duplicates**: Look for hidden or deactivated nodes that might still trigger emails.

3. **Inspect execution logs**: Compare timestamps to confirm if emails are sent during the same execution.

If the issue persists, try recreating the workflow or switching to a different email node (e.g., SMTP) as a temporary fix.

Let me know if this works!