Length, parseFloat & toFixed problem on version 0.211.2

[TheFSilver]

Hi guys,

Since the last update (0.211.2), I’m observing an odd behaviour around length, parseFloat & toFixed.

Have a look at the workflow below.

The workflow

This workflow should return the below data:

[
  {
    "myUpdatedVariableIsWorking": "4.20",
    "myVariableNotWorking1": "4.20",
    "myVariableNotWorking2": 4.2,
    "myVariableNotWorking3": "4.20"
  }
]

instead, we now get:

[
  {
    "myUpdatedVariableIsWorking": "4.20",
    "myVariableNotWorking1": "28.00",
    "myVariableNotWorking2": 28,
    "myVariableNotWorking3": 28
  }
]

Of course, the variable I have on many of my workflows is set like “myVariableNotWorking1”:
{{parseFloat($items('Code').length * 0.15).toFixed(2)}}

I don’t even know how many workflows are impacted yet but pretty please can we revert back to the old way?

Information on my n8n setup

• n8n version: 0.211.2
• Database: PostgreSQL
• Self-hosted on Heroku, as GitHub - sarveshpro/n8n-heroku: n8n docker implementation for heroku.

[TheFSilver]

I’ll just tag a few heads. that may help getting attention.
@jan @MutedJam @maxT

[maxT]

@ivov can you take a peek at this?

[jan]

Fix got released with [email protected]