Bug with expression editor calculation


So this workflow has a bug which happens every time.
As soon as you add the second “" it crashes. Before then when adding the first "” it starts to slow down.

Calculation is done in the SET node.

ps. I reproduced it after another user experienced this issue. That was on an older version (184)

Information on your n8n setup

  • n8n version: 194
  • Database you’re using (default: SQLite): postgres
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker
1 Like

Hi @BramKn, thanks so much for reporting this!

@Mutasem was looking into cases of the UI slowing down recently, could you perhaps take a look into what might be causing this?

1 Like

Thanks @MutedJam … Will try to look into it soon


Hi @Mutasem

Any clue what it is causing this?
Just had it again where I try to divide 2 values coming from a few nodes back. Also heard by PC ramping up and going bonkers on 1 core. (nothing else really running and the timing was perfect)

Actually after writing this, I went back to the tab and it started going crazy again on one core. So something is not right with this expression editor in combination with deviding 2 values from nodes before it(referencing the node and then the data not simply json coming in)

Hey @BramKn,

Oddly enough this is something I ran into last year when creating a quote tool using n8n, I ended up writing the expressions in a text editor and pasting them in as once in everything works great.

I have not seen any fix for this come in yet but I know @Mutasem has been busy other tasks so it will likely take a bit longer.

Hi @Jon

Thanks for the tip, will try that next time.
The most frustrating thing is when you forget this is an issue and the whole workflow is gone because of course I forget to save. :sweat_smile:

I remember the pain well, I probably should have reported it at the time.

you are forgiven. Now work your magic and fix it :wink: :rofl:

Looked into this. Seems to be related to how expressions resolve and still unclear to me what the root cause is… But it works with new syntax. You can use that instead.

1 Like

The new syntax looks good, any docs on that?


1 Like