It has a silly logic Merge node error at version 0.180.0 and newer one

Questions
1

I do not know what cause this, but I will show you what happened

  • It 's very serious! It could make so many logical workflows stop without reason
  • It takes me several hours to test in these version.
  • Version 0.179.0 does not has this error.
    (Now I come back to 0.179.0)

You could see at this case. My workflow stop at “Set” node without reason.
It just stop without logical for “Set” and “Merge” node. It’s so silly!

Look at my workflow:
chrome_xlCwrwtMPS

You could test with my workflow and execution data
But I bet it is the same with something has logic in “Merge” node (or “Set” node)

Execution at webhook:

[
  {
    "headers": {
      "connection": "Keep-Alive",
      "accept-encoding": "gzip",
      "cf-ipcountry": "HK",
      "cf-ray": "7184ea700d744d3f-SIN",
      "x-forwarded-proto": "https, https",
      "cf-visitor": "{\"scheme\":\"https\"}",
      "accept": "application/json,text/*;q=0.99",
      "user-agent": "axios/0.21.4",
      "cdn-loop": "cloudflare",
    },
    "params": {},
    "query": {
      "stream-name": "danntwoorg218931"
    },
    "body": {}
  }
]

This is my workflow:

2

Hey @cmdntd987, I am sorry to hear you’re having trouble. When running your workflow, did you by any chance see the error message described here?

1 Like
3

I think that 's it.
You could merge my topic to, because mine has execution data for that issue.

It looks like merge node misunderstood that the before node (set) was done, and have undefined data. It looks like there a single route forced to run, instead of full route (set node and zulip node, includes) or more to merge.

Anyway, I think that is a very serious issue.

1 Like
4

Good news, this should be solved soon. [email protected] containing two fixes for this has been released and is currently being built. It should become available in the next 30 to 40 minutes.

1 Like