#1: The dependencies test does not seem to work in this particular case. I have a variable named "test_result" which is set in a trigger action from the state of a z-wave module. The following image shows that when I right-click on the variable and check for dependencies, I am informed that there are none.
The next image shows that the variable is, in fact, set in the trigger action. The image also illustrates...
#2 The display within the GUI of device ID's instead of device names and variable ID's instead of variable names. You might argue that this is a feature, not a bug, but I it is at least a serious mis-feature. It reminds me of the late 1960's when I had to keep track of the numerical memory locations of my variables when programming. Later we got compilers which introduced the freedom of keeping track of variables by variable names. This was a marked improvement. Having to use and keep track of these ID numbers in Indigo seems like a 50-year throwback.