# Merge + noop + http request causes stragen behavior

**URL:** <https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807>\
**Category:** Questions\
**Tags:** merge\
**Created:** [July 31, 2023, 7:56pm UTC](https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807 "2023-07-31T19:56:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ricardo\_ned](https://avatars.discourse-cdn.com/v4/letter/r/50afbb/32.png) [@ricardo\_ned](https://community.n8n.io/u/ricardo_ned)\
**Post date:** [July 31, 2023, 7:56pm UTC](https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807/1 "2023-07-31T19:56:05Z")

</div>

## Describe the problem/error/question

Hi all, I’m having some trouble whith some workflows, I have two workflows, the only diff is a noop node, but they get wrong outputs, both of them.

wf1 wo/noop:  
Should output 1 item, but outputs 0  
wf2 w/noop  
Should output 1 item, but outputs 2

## What is the error message (if any)?

Output:

```auto

```

Cause

```auto

```

Stack

```auto

```

## Please share your workflow

wf wo/noop

## Share the output returned by the last node

## Information on your n8n setup

- **n8n version:**  
0.233.1
- **Database (default: SQLite):**  
default
- **n8n EXECUTIONS\_PROCESS setting (default: own, main):**  
where do I see this?
- **Running n8n via (Docker, npm, n8n cloud, desktop app):**  
n8n cloud
- **Operating system:**

---

<div class="post-metadata">

**Author:** ![jan](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/jan/32/9_2.png) [@jan](https://community.n8n.io/u/jan)\
**Post date:** [July 31, 2023, 9:28pm UTC](https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807/3 "2023-07-31T21:28:07Z")

</div>

Welcome to the community @ricardo_ned!

Please fill out the template. Especially the information about your n8n setup. We will then have a look at your question. Thanks!

---

<div class="post-metadata">

**Author:** ![ricardo\_ned](https://avatars.discourse-cdn.com/v4/letter/r/50afbb/32.png) [@ricardo\_ned](https://community.n8n.io/u/ricardo_ned)\
**Post date:** [July 31, 2023, 11:08pm UTC](https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807/4 "2023-07-31T23:08:14Z")

</div>

Hi, filled the missing info.

---

<div class="post-metadata">

**Author:** ![MutedJam](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/mutedjam/32/70851_2.png) [@MutedJam](https://community.n8n.io/u/MutedJam)\
**Post date:** [August 1, 2023, 8:23am UTC](https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807/5 "2023-08-01T08:23:55Z")

</div>

Hey @ricardo_ned, perhaps you want to head to your [n8n cloud dashboard](https://app.n8n.cloud/manage) and update to n8n version 1?

This version will introduce a new execution order which will affect nodes with multiple inputs (like the Merge node):

> **[Execution order - n8n v1.0 migration guide | n8n Docs](https://docs.n8n.io/1-0-migration-checklist/#execution-order)**
>
> This document provides a summary of what you should be aware of before updating to version 1.0 of n8n. | What's new in version 1

Once you have updated to v1, your example workflows will return the single item you expect.

Result of workflow 1:

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/b/3/b3873c3fda2018af2c2edc07fff4aa9cd295356c.png)

Result of workflow 2:

 ![image](https://europe1.discourse-cdn.com/n8n/original/3X/4/4/44002bec18148933a18362715234f15e14105db6.png)

---

<div class="post-metadata">

**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\
**Post date:** [October 30, 2023, 8:24am UTC](https://community.n8n.io/t/merge-noop-http-request-causes-stragen-behavior/28807/6 "2023-10-30T08:24:25Z")

</div>

Closed on October 30, 2023, 8:24am UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.