False Warning for Global Variables

MindStudio IDE Bug Reports
1

I’m running into a consistent issue with global variable warnings in Mindstudio. Whenever I reference a global variable in any block, I get a warning saying the variable “is referenced but does not exist” - even though the global variable is actually there and functioning perfectly fine.

The warning appears regardless of which workflow I’m working in, and it’s kind of misleading since the variables work as expected when the workflow runs. It seems like there might be a validation issue where the system isn’t properly recognizing existing global variables during the design phase.

This creates unnecessary confusion during development since the warning suggests something is broken when everything is actually working correctly.

Thanks for looking into this!

1 Like
2

+1
Indeed! Had the same issue today - was trying to figure it out for couple of minutes, before i realized it is just a bug in the warning and the variable is normally workig.

3

This should be fixed now. There are some types of variables where the IDE isn’t always able to reliably determine whether or not they have been set (user variables, global variables, variables set within custom functions, etc.), and sometimes throws false errors. The errors shown in the IDE are always for informational purposes only—they never affect that compilation or execution of an agent.