Why Does the 'Date & Time' Node Trigger Duplicate Workflow Execution?

It sounds like what you’re experiencing isn’t a bug in n8n but rather a result of how the Date & Time node (and n8n in general) handles data. Here are a few points to consider:

• Item Processing:
  In n8n every node processes an array of items. Even if you expect a single output, if more than one item is passed into the Date & Time node, it will output a corresponding date/time value for each one. Check your upstream nodes to ensure you’re not inadvertently passing duplicate items to it.

• Include Input Fields Option:
  The Date & Time node has an option like “Include Input Fields.” If this is enabled, the node will add the current date/time (in your chosen format) on top of each input item. This might give the impression that the node is “triggering” parts of your workflow more than once if you didn’t intend to carry over each input item.

• Workflow Structure:
  Verify that your workflow isn’t set up to re-trigger downstream nodes with multiple items. If the Date & Time node is used solely for generating a single date/time value, consider either filtering the input so that only one item reaches it or adjusting the configuration so that extraneous data isn’t being passed along.

In summary, the behavior is due to n8n’s item-based execution model and the node’s configuration options rather than an intentional “double trigger” or a bug. Adjusting your workflow to ensure only a single item is passed (or modifying the node’s settings) should resolve the issue.

Hope this helps!