Variables defined in function node are not holding values on 0.198.2

[Roney_Dsilva]

Hi @Jon ,
Sadly due to the complexity of our workflows we are unable to use an external data source.
Currently, we have downgraded all our n8n instances to 0.197.1

Looking back at several other topics, I see that others too were using the function/Set node in a similar fashion.
Could you please relay to the team that it’s a crucial feature that would be of great help in several use cases.

Below are the topics where similar use cases have been discussed, all of which are not working anymore after 0.198.2:

Is there something like global variable?

I want to have global variables when the workflow starts and be able to change a variable in the next node or add a new variable, is it possible? I think of using set node when the workflow starts and he will act as global variables

Global variables

Describe the issue/error/question I’m needing to have global variables shareable between workflow example URL, access_token I need to implement the token manually update, auth2 doesn’t answer me What is the error message (if any)? no Please share the workflow (Select the nodes and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow respectively) Share the output returned by the last node Information on your n8n setup n8n version: latest Database…

Global Variable Support

The idea is: To create a resource for global variables with various scopes. 1. Scoped to the workflow, and 2. Scoped to the Execution, 3 Scoped to the User. it could be access similar to the way we use Luxon. allowing you to instantly … do something like merge “number of monkeys today = {{$var.variableName}}” into a report. My use case: Managing a counter is a really usefull programming concept, weather it is how many times an error occurred, how many times a loop ran, etc. And inside N8N it…

A Global variable node/feature

The idea is: A Global variable node whose data can be manipulated from other nodes especially from the newly introduced Code node My use case: In several instances we require to use a variable to store dynamic data, that can be destroyed once the workflow execution finishes. I think it would be beneficial to add this because: This feature was working fine until version 0.198 was introduced with the new code node. Any resources to support this? Are you willing to work on this? yes