Variable Selector doesn't work in Edit Expression window

[rafitamolin]

Describe the bug
Variable Selector doesn't work in Edit Expression window.

To Reproduce
Steps to reproduce the behavior:

1. For example, create a "Send a text message" Telegram node and connect it.
2. Open the created node, and you'll see "No input data yet - Execute previous nodes". Click that button.
3. In the "text" field of the message to be sent to Telegram, click on "Expression" instead of Fixed". Then, click
4. Variable selector is empty even having executed previous nodes.
   

Expected behavior
Variable selector should display all nodes and relevant info.

Environment (please complete the following information):

• OS: Ubuntu Linux 22.04
• n8n Version 0.221.0
• Node.js Version 18.15.0
• Database system SQLite
• Operation mode own

[Joffcom]

Hey @rafitamolin,

I have just taken a look and I am not able to reproduce this one, If you go to open an expression before running the previous node do you see anything? You should in theory always see the Current Node and any parameters and the names of previous nodes.

Do you see any errors in the browser dev console or the n8n log?

[rafitamolin]

@Joffcom I've just tried and before running previous nodes, I can properly see the variable selectors without any problem. But when executing the workflow/previous nodes I can't.

I believe it's because my Telegram send-message trigger is behind a if node, and the normal situation is for the if to return "false", as you can see here:

But I think even though returning false, the variable selector should display all nodes in the workflow, could you check if you can reproduce it via a IF node like me?

[Joffcom]

Hey @rafitamolin

Can you share your workflow? Coming off an if node shouldn't make a difference as you would still be able to access the current nodes parameters but it is always possible there is some odd bug.

If we can get the full workflow we can try the same think you are in the same way to see what happens.

[rafitamolin]

@Joffcom Here's the workflow URL so you can import it, I had to edit sensitive info from it but I still can reproduce the issue from this edited version:

https://raw.githubusercontent.com/rafitamolin/chatgpt-telegram/main/testeee.json

If by any reason you can't still reproduce it, here's a video file I recorded:

msedge_HaXKPpHpy8.mp4

[Joffcom]

Hey @rafitamolin,

So the good news is I can reproduce the issue with your workflow and I have managed to use it to create a smaller version

For now if you use 0.220.1 this will work as expected, Our internal dev ticket for this one is N8N-6284

[janober]

Fix got released with [email protected]

[Joffcom]

Hey @rafitamolin,

This should now be resolved, I am going to mark this one as closed. If you still this issue let me know and we can open the issue again.