Set variables - null

[dhtbrowne]

Hey team,

Getting some strange behaviour from the set variables node.
This is my node chain:

taskID and projectID are definitely being set by the setvariable node with values that aren’t null earlier in the chain:

But when I go to the node that is erroring and check the input under variables… It seems like most of the variables set at that stage are now null:

I have two other set variables nodes that are running in this path and my first thought was that they might be overwriting the variables, but they’re both setting different variables:

So then I though well does the setvariables wipe away all other variables set in previous nodes then (which would be a pain). But in this other run it was successful and that just has one less setvariables node than the above example and that seems to be working correctly:

Any ideas what could be overwriting the other setvariables or causing them to be null?

[Raian]

Hi! I’ll reach out to the development team to clarify the details and get back to you with an answer or solution by the end of the day.

[Raian]

I checked with the developers, and this is a bug that is currently being fixed.

In the meantime, try using the variable from the Data window in the 1$.variable format instead of _.variable. This should likely resolve the issue.

[dhtbrowne]

Cool as. Can you let me know when it’s fixed? I can’t really grab it from a specific node because the way I’m using the set variable is basically it pulls a record from the database and then it goes through different chains to add in missing stuff based on the filters, adding them into set variable as it goes, then updates the database and Toggl and the end so I never really know which chain it’s come from. I’ll wait for the fix and just manually resolve errors until then. It only runs a few times a day.

[Oleg]

The fix is live. Please check it now.