Describe the problem/error/question

Active workflow with a single Schedule Trigger fires two executions at the exact same scheduled instant. One execution uses the current workflow definition, the other uses an outdated snapshot of the same workflow (different activeVersionId from before recent edits). Both executions have mode: "trigger" and the workflow has exactly one scheduled trigger configured (triggerCount: 1).

Same underlying mechanism as #19169 (IMAP), but for Schedule triggers.

Workarounds tried, both insufficient as a permanent fix:

• Toggling Active off → on (with several seconds wait in between): did NOT resolve the duplicate — the next scheduled fire still produced two executions, one with the outdated snapshot.
• Deleting the workflow and recreating it from scratch: resolves the duplicate at that moment, but the issue reappears after the new workflow has been edited and saved a few times over the following days.

What is the error message (if any)?

No error. Both executions complete with status: "success". The problem is silent duplication.

Please share your workflow/screenshots/recording

Not sharing the full workflow (business logic + credentials references). Relevant shape:

• 1× n8n-nodes-base.scheduleTrigger (single daily fire)
• 1× n8n-nodes-base.manualTrigger (used during development)
• Workflow body: file IO (azureStorage, readWriteFile), batched processing (splitInBatches), Slack notification
• No webhook node, no external executeWorkflow callers
• Saved/edited multiple times per week

triggerCount reported as 1 via the API — n8n itself believes there is only one trigger registered.

Share the output returned by the last node

N/A — both executions complete successfully; the symptom is two parallel executions, not a data problem.

Reproduction (narrowed-down conditions)

1. Active workflow with a single Schedule Trigger
2. Edit and save the workflow multiple times over several days without toggling Active off/on between edits
3. At some point, the next scheduled fire produces two mode: trigger executions starting within tens of milliseconds of each other
4. Both executions reference the same workflowId; one uses the current activeVersionId, the other a prior version
5. State persists across days. Toggling Active off → on does not resolve it. Deleting and recreating the workflow resolves it temporarily but the issue re-emerges after further edits.

Evidence from a single morning fire (2026-05-18)

Δt between the two trigger fires: 26 ms. Both fired at the same scheduled minute. Single Schedule Trigger node configured.

Debug info

core

• n8nVersion: 2.20.7
• platform: docker (self-hosted)
• nodeJsVersion: 24.14.1
• nodeEnv: production
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: enterprise (production)
• consumerId: 1556fd7e-0894-42f2-8a0c-221df9669b9e

storage

• success: all
• error: all
• progress: false
• manual: true
• binaryMode: filesystem

pruning

• enabled: true
• maxAge: 336 hours
• maxCount: 10000 executions

client

• userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/146.0.0.0 safari/537.36
• isTouchDevice: false

security

• secureCookie: false

cluster

• instanceCount: 1
• versions: 2.20.7
• instances:
  • instanceKey: ec5bba91-4e6b-438e-a763-7bf372b7cacc, hostId: main-17aaf4eac745, instanceType: main, instanceRole: leader, version: 2.20.7
• checks:
  • check: hostid-clash, status: succeeded, warnings: -
  • check: lifecycle, status: succeeded, warnings: -
  • check: split-brain, status: succeeded, warnings: -
  • check: version-mismatch, status: succeeded, warnings: -

Generated at: 2026-05-18T08:08:54.927Z