Another issue I encounter sometimes…
- I place the sticky notes/nodes where they should be
- Click on Save
- Reload
- They revert back to where they were previously
[This behavior continues in some cases even after clearing browser cache]
Very excited about the update. This is the first time I’ve been able to use my phone to work on a flow! It’s not often that I don’t have a computer, but there has been more than one time I needed to update a flow or troubleshoot it and I only had my phone.
Very happy say I’m now able to do that. I have a few flows that take a good 20 seconds to load, and looking forward to that performance improvement. Would love to know when the n8n team feels comfortable with it’s stability, so I can try it in production.
I wonder if this is a step towards handling async workflows and parallelism.
Just updated to 1.68.0 a few hours ago, I have this major problem
When I add new fields to Airtable and I wanna map them, I usually just click on “Refresh Column list” and it loads new fields keeping the old ones there with their respective value, unless the field name changes, then it removes them and puts the updated empty ones in order.
This time when I clicked it, it just removed all the mapped data in all the fields, and wiped everything clean…
Tried adding the new fields to the node’s json code, but it didn’t work…
Please let me know how can I fix this.
For future updates: It would be great for it to be able to just replace the name, instead of cleaning the input (In case I change a fields from “phone” to “phone_number” for example, using fields ids as a reference for that…)
1 Like
Found a workaround for this
I just switch this to “Map Automatically”, then switch back to manually, and it fetches the new fields without removing the previous values…
1 Like
If you rewrite the canvas please consider free movement for lines between nodes. I think many times it’s a lot of spaghetti. Supporting lines with an angle would help to make it easier to understand. Also custom colors for the Note feature would be nice. A lot of times I want to bend the lines between nodes out of the way.
Or another suggestion, make it possible to also connect on the bottom/top of a node instead of left and right.
Cheers.
Hey Hans, we’ve all been there! As a workaround, you can use the ‘no operation’ node to reroute connectors.
One thing I’ve noticed is when I open a module it always defaults to Table view… It would be nice if it would keep the setting last set by the user. For example, I almost exclusively use JSON, but I’m sure others have their preferences as well.
The new canvas is MUCH faster than the old canvas. GREAT job!
My biggest “quibble” is with the change to the default routes for the path between modules. A lot of my automations require loops, and the old canvas allowed me to create “concentric” loops that were easy to understand:
Old Canvas:
In the new canvas, the paths always take the shortest route, which usually means they go through the middle of the layout and intersect with modules and other paths:
New Canvas:
If there were a preference setting to use the old path routing, I would definitely turn it on.
Here’s the code for this mockup in case anyone wants to play around with it:
1 Like
While we’re requesting features, please please please add a “pause” capability to connections. (I know, it’s not exactly a canvas feature, but it’s canvas adjacent…)
When debugging we often need to test only part of a workflow. Right now the only way to disable part of a flow is to disconnect it. That means we have to remember how everything is supposed to be connected and remember to reconnect everything when we’re done debugging.
If we could just pause connections it would make that process a lot less error prone. Especially if paused connections were a different color than active connections.
Lee
1 Like
Also while we’re requesting features, it would be a game-changer for organizing large flows to be able to group several modules together behind a single icon.
Right now many devs place different color sticky notes behind groups of modules. That really makes it much easier to understand a large workflow, but it’s kind of a hack and it doesn’t really hide complexity.
What I propose is a new purely cosmetic module called a “group”. The developer places a group on the main canvas, and specifies the number and names of the inputs and outputs as well as the name of the group.
Then when the developer double clicks the group it opens up a “sub canvas”. Inputs are on the left edge, outputs are on the right edge. Developers can paste in a set of modules and connect the inputs and outputs appropriately.
When closed, the group hides the complexity of what’s inside. When open, the developer can focus their attention JUST on what’s happening inside and ignore what’s outside.
So for example I could paste this set of modules into a group with one input and one output:
Or I could paste this set into a group that has two inputs and three outputs:
Lee
1 Like
Since using the new canvas, every once in awhile I’ve tried moving modules, saving changes, and then when I run the process again and reload it the modules have moved on the canvas back to where they were. It’s not always, and I haven’t been able to isolate why, but I wanted to report it just in case it’s something y’all have noticed as well…
1 Like
I’ve noticed the same thing, but only when I move them as a group. I’ve also noticed that when I do move them as a group the canvas doesn’t recognize any changes, and so the “Save” button doesn’t light up to allow me to save that change. And as soon as I do something that the canvas acknowledges as a change, it reverts the grouped moved nodes to their previous spot.
One other item I’ve noticed is that if I move the nodes one at a time the canvas does recognize the changes and I’m able to save.
I have to say the speed difference is astonishing. There were some complicated flows with a decent amount of data retained in the flow (on the old canvas) that would cause it to take more than 20 seconds to load. It made updating and troubleshooting a long and tedious process. Now (with the new canvas), the longest part is me trying to figure out how to do the thing or fix the the thing I just did. Have to say a very happy thank you for the new canvas n8n team!
Yep from time to time it happens to me as well…
I have just updated this topic to reflect that as of 1.70.0, the new canvas is now in Beta, and that it’s now the default for all new users.
New changes and features:
- Greatly improved load performance
- Connections now loop backwards the same way they did in v1 and have a middle arrow to point the direction
- Selection is now navigable using keyboard arrows
- Several bug fixes
Please keep reporting your issues here 