N8n set node input obviously outputting wrong data

Questions
1

Describe the problem/error/question

Does someone know what’s happening?

It’s like this workflow unexpectedly retains memory of previous executions.

The input is an n8n form.

I’ve tried keeping the form in a subworkflow, then using a completely new workflow so that there’s no chance executions carry over.

But the issue still persists. I input one thing into a set node and it comes out something else (this “something else” has been correct output before, but not in this very current execution)

This is not making sense

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hey @KingSaud hope all is good.

which workflow? Would you like to share the workflow and screenshot the problem?

4

Hi @KingSaud

This is a very common point of confusion. The workflow isn’t remembering old data; you are just re-running it in the editor with old test data .

When you press “Execute Workflow,” n8n uses the last sample data it received. It doesn’t wait for a new form submission.

Here is the simple fix:

Click your Form Trigger node.
Click “Listen for Test Event” .
Submit your form again while it is listening .

This will load your new data into the editor for testing.
Remember, once your workflow is Active , it will always use the correct, live data for every real execution.

If you found this helpful, please mark it as the solution and give it a like .