Item linking and merge node

[atwork1]

Describe the problem/error/question

Items lose their item linkage.
In my opinion the items should not lose the item linking after the merge node if the clash handling is set to prefer certain input (if at all).

What is the error message (if any)?

Multiple matching items for expression [item 1]

The code here won’t work because it uses .item and n8n can’t figure out the matching item. (There are multiple possible matches)

Try using .first(), .last() or .all()[index] instead of .item or reference a different node.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

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

[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:

[barn4k]

Just executed it on v1.37.3 and didn’t get any issues

[atwork1]

lol, the same.

the quoted error is from this workflow, which I built after running into the same issue in another wf.

the container was last (re)started on the 24th.

this is from the execution history. can it be exported?

The previously successfull runs were all without the last node.

UI glitch?

Edit:
on retry, with currently saved wf:

[dougieled]

Also seeing something similar since the newest updates. Did you get a fix in for the time being? Could you post it if so. Cheers

[atwork1]

@dougieled

Did you get a fix in for the time being?

when I run it NOW it seems to work.
For the actual WF where I previously ran into the issue I manually linked them with a code node, see below:

Edit: in this case I add the same binary to each item.