Runtime Variable Not Clearing Between Runs (Possible Caching Issue?)

Support
1

Runtime Variable Not Clearing Between Runs (Possible Caching Issue?)

I’ve built a workflow that calculates commission values based on a given sellingPrice. It supports multiple optional entries (e.g., sellingPrice01, sellingPrice02, sellingPrice03, etc.). I’m using both global and runtime variables throughout the flow.

One issue I’m encountering is that runtime variables appear to persist between runs, which is causing logic failures—especially with optional inputs.

:counterclockwise_arrows_button: Example Scenario

In my Logic Block, I’m checking if an optional variable like sellingPrice03 is empty:

{{isEmpty sellingPrice03}}

I expect:

  • true → if the user didn’t enter a value → then jump to the Main Menu
  • false → if a value was entered → proceed to the next step

But even if the variable wasn’t entered on a new run, the system behaves as if it still has a value from the previous run.

:wrench: What I’ve Tried

  • Confirmed sellingPrice03 is not a global variable
  • Checked input flow and logic block connections
  • Suspect that caching or variable persistence is the issue

:red_question_mark:Question

How can I ensure runtime variables are cleared or reset to null at the start of each run?

Is there a best practice to avoid unwanted persistence, or a block/action I can add at the beginning to explicitly clear certain variables?

2

What appears in the debugger when the logic block executes?

3

I changed tactics and created a function to reset the variables to 0 and then used the gt and lt handlebars to decide next steps. The debugger was correctly returning True when the isEmpty handlebar was used. There did not seem to be a corresponding isNotEmpty so it is possible I used the incorrect syntax for the second destination. I moved on the reset variable function which created the desired result.