Bug Description

I use the Remove Duplicates node with the Remove Items Processed in Previous Executions action. When the maximum history size is reached, the node gets stuck and error's out on every subsequent execution.

To Reproduce

1. Create a new workflow with manual trigger -> code node producing an array of objects (see code below) -> Remove Duplicates with History Size set to 10 and Value to Dedupe On is {{ $json.id }}
2. Execute workflow 3 times

Code node:

return Array.from({ length: 4 }, () => ({
  json: {
    id: Math.floor(100000 + Math.random() * 900000)
  }
}));

Expected behavior

I expect the Remove Duplicates node will maintain history of 10 items and it will remove the oldest ones when it needs to create room for new items. It will not throw an error when the limit is reached.

Debug Info

Debug info

core

• n8nVersion: 2.38.3
• platform: npm
• nodeJsVersion: 24.10.0
• nodeEnv: undefined
• database: sqlite
• executionMode: regular
• concurrency: -1
• license: community
• consumerId: unknown

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/153.0.0.0 safari/537.36
• isTouchDevice: false

cluster

• instanceCount: 1
• versions: 2.38.3
• instances:
  • instanceKey: 19829420-e90f-4465-af75-48f6f9850251, hostId: main-fF4suIhw2KpW7AOH, instanceType: main, instanceRole: leader, version: 2.38.3
• 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-09-11T13:25:26.238Z

Operating System

MacOs

n8n Version

2.38.3

Node.js Version

24.18.0

Database

SQLite (default)

Execution mode

main (default)

Hosting

self hosted