search

n8n-io / n8n

Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
https://n8n.io
Other
45.7k stars 6.36k forks source link

SERIOUS bug in UI 0.214.0 - Node connections are not saved #5359

Closed ed-parsadanyan closed 1 year ago

ed-parsadanyan commented 1 year ago

Describe the bug In the n8n Docker version 0.214.0 node connections are not saved. Check the webm video attached

To Reproduce Steps to reproduce the behavior:

  1. Create new workflow
  2. Add a bunch of nodes and try connection them
  3. Observe that new connections don't trigger workflow save button
  4. On workflow reload all connections are gone

Expected behavior Node connections stay in the workflow after they are added.

Environment (please complete the following information):

Additional context Video

Joffcom commented 1 year ago

Hey @ed-parsadanyan

Thanks for the report, just tried to view the video but it was still processing.

Out of interest what browser are you using? I made a couple of workflows this morning and didn't run into this issue.

ed-parsadanyan commented 1 year ago

Hey @ed-parsadanyan

Thanks for the report, just tried to view the video but it was still processing.

Out of interest what browser are you using? I made a couple of workflows this morning and didn't run into this issue.

Yes, google doesn't show the webm video for some reason. But when you download it then it works. I'm using Chrome and had to revert to 0.213.0 to fix the issue.

The problem is with a specific way of adding node connections (as shown in the video). When you add a separate node and connect two nodes, then it doesn't work.

First, add 2 separate nodes: vlcsnap-2023-02-04-17h34m48s567

After connecting them nothing happens and "Save" button is not activated. vlcsnap-2023-02-04-17h35m07s887

ed-parsadanyan commented 1 year ago

Hey @ed-parsadanyan

Thanks for the report, just tried to view the video but it was still processing.

Out of interest what browser are you using? I made a couple of workflows this morning and didn't run into this issue.

I tried a bit further. Looks like the issue is limited to the Merge Node. Other nodes look fine

janober commented 1 year ago

Thanks a lot for that information. I was also wondering. I tried to reproduce this bug earlier but was totally unable to. Then I tried to build a workflow a few hours afterward regularly, and then I also ran into that issue. It was also with the Merge-Node. We will release a bug-fix version on Monday with a fix.

janober commented 1 year ago

Fix got released with n8n@0.214.1