Issue with Parameter dropdown when using expression in any field

Questions
1

Hi,

I have noticed a weird isssue lately. Has been there for a bit but always thought it was just random. Now I got to reproduce it.

I have tested it with 2 nodes and it seems a general issue.
Normally there is nothing wrong we can nicely select parameter values from dropdowns

image
image382×748 14.2 KB

But as soon as you change one of the values to an expression that doesn’t have any data at that point it will break all parameters that work with the dropdowns. This is a bit of a pain the ass while developing.

image
image351×740 14.5 KB

When the node before or when the node referenced has ran there is no issue.
Tested with Baserow node and a community node, both have the exact same issue, so I think it is a general issue.

image

image
image382×547 12 KB

Information on your n8n setup

  • n8n version: 1.3.1 & 1.2.1 & 1.4
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): Queue & regular main
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu
2

Hi @BramKn :wave: Thanks for reporting this - I’ve confirmed this happening as well for me on 1.3.1 and 1.4.0. I’ve flagged this with our engineering team to take a closer look into why this is happening, and I’ll be back as soon as I can with updates!

2 Likes
4

Hi @EmeraldHerald

Do you have an update on this?

5

Hi @BramKn :wave: Not yet, really, I’m afraid - the issue has been triaged, but work hasn’t started yet :bowing_man:

2 Likes
6

Hi @EmeraldHerald

Is there any update on this?

7

It would still be the same status I’m afraid - I can give the engineering team a poke to see if there’s any kind of estimate :+1:

1 Like
8

Was fixed in v1.11 or v1.12 :partying_face:

Thanks @Jon for telling me :slight_smile:

2 Likes
9

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.