Clean up "Remove Duplicate Node" history

[Alan_Cheung1]

Hi everybody,
I have a question aboue “remove duplicate node” in option “Remove Items Processed in Previous Executions” → Keep item where “Value is new”

Describe the problem/error/question

I can run this node very smooth. But how to clean up the history. No matter I quite the workflow or reset chat session. The final output will remember my last result. . Now, my result always keep in “Discard” tab in output if i use the same data set.

Wat is the error message (if any)?

Please share your workflow

Share the output returned by the last node

[
{
“email”: “[email protected]”
},
{
“email”: “[email protected]”
}
]

[Anshul_Namdev]

Hi @Alan_Cheung1 Welcome!
have you tried adding a remove duplicate node with the operation set as clear seduplication history > mode: clean database then run it whenever you want to reset the history.

Remove Duplicates node documentation | n8n Docs

[houda_ben]

Hi @Alan_Cheung1

The “Remove Items Processed in Previous Executions” operation stores a history of every value it has seen in n8n’s database, this persists across executions by design, which is why your emails keep landing in Discard.

Two fixes:

1. Switch the operation to “Clear Deduplication History” and execute the node once to wipe the history. Then switch back.

2. If you don’t need cross-execution memory, use “Remove Items Repeated Within Current Input” instead, no memory between runs.

[Mamta_Bankoti]

This isn’t an error, it’s just how the node works. It remembers the items it has already processed, so when you run the same data again, those emails go to the Discard tab. To fix it, simply clear or reset the node’s data, or use a new node.