Super Weird Output - Might be Bug

[Bryce_Claudin]

Idk how to describe this issue besides showing you in a very quick video.
See Video

I call it a bug in the video. But it might not be. If you’re an expert, brownie points if you can educate me on what is actually going on here

To replicate yourself:

main workflow:

Make an http request to the workflow above:

(If you’re wondering why I even have this setup like this, I duplicated the workflow and removed my sensitive data. This is a real workflow)

Information on your n8n setup

• n8n version: 1.80.5
• Database (default: SQLite): SQLite
• self hosted using docker

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[Knight]

This is definitely a bug. I’m guessing it’s happening because the object being used has the same reference as the one from the previous node. So instead of modifying what you thought was a new object, you’re actually modifying the data from the previous node.